Use of this library is not recommended if you need to interact with an MSSQL database (because UnixODBC and FreeTDS are flaky).
You should instead check out gomssql-python which removes the need for UnixODBC and FreeTDS.
If you're interacting with some other ODBC-exposed database and you know what you're doing though, please fill your boots.
The purpose of this module is to provide a Python interface to the Golang goodbc module.
It was made very easy with the help of the Golang gopy module.
This version (0.91) is the last version to support Python 2; all versions after this have been subject to a refactor and support Python 3 only.
- Python command needs to be prefixed with GODEBUG=cgocheck=0 (or have that in the environment)
- Go 1.13
- Python 2.7+
- pip
- virtualenvwrapper
- pkgconfig/pkg-config
- unixodbc
- Linux:
apt-get install unixodbc unixodbc-dev freetds-bin freetds-dev
- OSX:
brew install freetds --with-unixodbc
- Linux:
python -m pip install goodbc-python
python setup.py install
python setup.py bdist_wheel
Ensure pkg-config is installed Ensure unixodbc is installed
mkvirtualenvwrapper -p (/path/to/pypy) goodbc-python
pip install -r requirements-dev.txt
./build.sh
GODEBUG=cgocheck=0 py.test -v
- gopy doesn't like Go interfaces; so make sure you don't have any public (exported) interfaces
- this includes a struct with a public property that may eventually lead to an interface
To create an ODBC session in Python do the following:
from goodbc_python import Connection
ip = "127.0.0.1"
port = 5432
database = "test"
username = "test"
password = "test"
conn_str = """
DRIVER={FreeTDS};
TDS_VERSION=8.0;
SERVER=%s;
Port=%i;
DATABASE=%s;
UID=%s;
PWD=%s;
""" % (
ip, port, database,
username, password
).replace('\n', '').replace(' ', '')
connection = Connection(conn_str)
cursor = connection.cursor()
query = "SELECT NOW()"
cursor.execute(query)
records = cursor.fetchall()
print("Records:")
print(records)
cursor.close()
connection.close()
This seems to leak quite badly when trying to connect and query a bad IP address when using the FreeTDS driver.
FreeTDS v1.1.17, their latest stable but the problem persists. It could very well be an interaction between goodbc and the driver. Not sure at this stage.
MOUNT_WORKSPACE=1 ./test.sh bash
./build.sh
py.test
py.test
./manual_test.sh
This will spin up a Docker container that tries to connect to a specific database (internal to FTP Solutions); if the database is not there it'll simply fail (which is a good way to manually test for leaking memory).