Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support turbodbc #56

Closed
pmetzner opened this issue Mar 14, 2017 · 6 comments
Closed

Support turbodbc #56

pmetzner opened this issue Mar 14, 2017 · 6 comments

Comments

@pmetzner
Copy link

pmetzner commented Mar 14, 2017

Currently only python 2.7 is supported by turbodbc and therefore for sqlalchemy-exasol, too.

Humble request: Since turbodbc now supports Python 3, can sqlalchemy-exasol extend the turbodbc support to Python 3, too?

@hoffmann
Copy link
Contributor

I have activated the tests for turbodbc and python 3.4. There are three errors, but they do not seem to be critical:

https://travis-ci.org/blue-yonder/sqlalchemy_exasol/jobs/211250660

Did you try to use/install sqlalchemy with turbodbc and got any errors on python 3.x?

@pmetzner
Copy link
Author

pmetzner commented Mar 15, 2017

Awesome! Already tested it yesterday, this works like a charm:

cnxn = connect(dns)
crsr = cnxn.cursor()
crsr.execute('select 42')
crsr.fetchall()

@pmetzner
Copy link
Author

Ah, I think I misread your question. I tried installing sqlalchemy-exasol[turbodbc] yesterday but it didn't offer the extra turbodbc. Now it did and it works. Did you change anything?

@pmetzner
Copy link
Author

I had some trouble with the DEFAULT_DRIVER_NAME in turbodbc.py, I hotfixed it in #57.

@bjoernmeier
Copy link
Contributor

Could you specify the problems you are having with the DEFAULT_DRIVER_NAME ?
As EXAODBC is the default driver name provided by EXASOL and their driver package and you can overwrite it in you connection string I do not see a problem so far.

@bjoernmeier
Copy link
Contributor

I close this ticket as python3 support is fixed and the default driver name can be overwritten.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants