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

Turbodbc support #50

Merged
merged 37 commits into from
Jul 15, 2016
Merged

Turbodbc support #50

merged 37 commits into from
Jul 15, 2016

Conversation

bjoernmeier
Copy link
Contributor

No description provided.

bjoernmeier and others added 30 commits June 23, 2016 19:02
if a schema is not provided as parameter or in the engine
use a SQL statement to detect the current schema
turbodbc requires the parameters for a sql statement as tuple,
in pyodbc you can use a tuple or provide the parameters directly.
To work with both we change it to tuples.
turbodbc returns a unicode string, so we have to convert it to int
if it is already an int it does not harm
added turbodbc examples
secure string with turbodbc connection string
use trusty as ubuntu precise uses a old gcc
run tests for turbodbc
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

Successfully merging this pull request may close these issues.

None yet

2 participants