Metadata-Version: 2.1
Name: pymssql-utils
Version: 0.0.7
Summary: pymssql-utils is a small library that wraps pymssql to make your life easier.
Home-page: https://github.com/invokermain/pymssql-utils
Author: Tim OSullivan
Author-email: tim@lanster.dev
License: GNU LGPLv2.1
Platform: UNKNOWN
Classifier: License :: OSI Approved :: GNU Lesser General Public License v2 (LGPLv2)
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: Database
Classifier: Typing :: Typed
Requires-Python: >=3.6
Description-Content-Type: text/markdown
Requires-Dist: pymssql (==2.1.*)
Requires-Dist: python-dateutil (==2.8.*)
Requires-Dist: orjson (==3.4.*)

# pymssql-utils (ALPHA)
_pymssql-utils_ is a small library that wraps
[pymssql](https://github.com/pymssql/pymssql) to make your life easier.
It provides a higher-level API, as well as a some utility methods,
so that you can spend less time thinking about connections and cursors
and more time thinking about your project.

This module's features:
* Higher-level API that reduces the amount of boilerplate.
* Baked-in sensible defaults and good usage patterns.
* Parses the SQL Types that _pymssql_ misses to native Python types.
* Makes it easy to serialize your data with
  [_orjson_](https://github.com/ijl/orjson).
* Provides you with simple and clear options for error handling.
* Proves utility functions,e.g. for building dynamic SQL queries.
* Fixing various edge case bugs that arise when using _pymssql_.
* Fully type hinted.

This module's enforced opinions (check these work for you):
* Each execution opens and closes a connection using _pymssql_'s
  context management.
* Execution data is returned as a dictionary, as accessing data by column name
  is clearer and simpler than by index.
* Converts numeric data to `float` as this is easier to work with than `Decimal`
  and for the vast majority of cases 'good enough'.


This library was created naturally over the course of a few years of using _pymssql_ in various projects.

Please raise any suggestions or issues via GitHub.

## Usage
### Installation

This library can be installed via pip: `pip install --upgrade pymssql-utils`.
This library requires `Python >= 3.6` and `Pip >= 19.3`.

### Quickstart

Executing a simple query, accessing the returned data and serialising to JSON:

```python
>>> import pymssqlutils as sql
>>> result = sql.query(
      "SELECT SYSDATETIMEOFFSET() as now",
      server="...",
      user="...",
      password="..."
    )
>>> result.ok
True
>>> result.data
[{'now': datetime.datetime(2021, 1, 21, 23, 31, 11, 272299, tzinfo=datetime.timezone.utc)}]
>>> result.data[0]['now']
datetime.datetime(2021, 1, 21, 23, 31, 11, 272299, tzinfo=datetime.timezone.utc)
>>> result.to_json()
'[{"now":"2021-01-21T23:31:11.272299+00:00"}]'
```

### Specifying Connection
There are two ways of specifying the connection parameters to the SQL Server:
1. Passing the required parameters
   ([see pymssql docs](https://pymssql.readthedocs.io/en/stable/ref/pymssql.html#pymssql.connect))
   into each of function calls (_query, execute & execute_many_) like in the quickstart example above.
   All kwargs passed to this methods are passed on to the `pymssql.connection()`.
2. Specify the connection parameters in the environment like the example below, note that parameters given
   explicitly will take precedence over connection parameters specified in the environment.

```python
import os
import pymssqlutils as sql

os.environ["MSSQL_SERVER"] = "sqlserver.mycompany.com"
os.environ["MSSQL_USER"] = "my_login"
os.environ["MSSQL_PASSWORD"] = "my_password123"

result = sql.execute("INSERT INTO mytable VALUES (1, 'test)")
```

### Executing SQL
This library provides three functions for executing SQL code:
`query`, `execute` & `execute_many`. These functions call _pymssql's_
`execute` or `executemany` functions with varying behaviour to fetching
result data or committing the transaction, see table below.

| Function      |   Wraps         |   commits     |  fetches     |
|---------------|-----------------|---------------|--------------|
| query         | execute         | False         |  True        |
| execute       | execute         | True          |  Optional    |
| execute_many  | execute_many    | True          |  False       |

Splitting `query` & `execute` into two functions based on whether the execution
commits or not is intended to make it clearer in your code
what your SQL execution is doing.

### Error handling (TODO)

### Utility Functions (TODO)

## Notes

### Why _pymssql_ when Microsoft officially recommends _pyodbc_ (opinion)?

The main difference between _pyodbc_ and _pymssql_ is the drivers they use.
The ODBC are newer and have various levels of support on differing linux distributions,
and if you develop for containers or distribute code onto different platforms
you can run into ODBC driver-related issues that FreeTDS tends to not have.

There are other minor reasons someone might prefer _pymssql_, e.g.:
 * _pymssql's_ parameter subsitution is done client-side improving operation visibility.
 * _pymssql_ also has support for MSSQL specific data types such as Datetimeoffset.

