ODBC transport doesn't work

[ibm]

ODBC transport doesn't work

[kadler]

Original comment by Kevin Adler (Bitbucket: kadler, GitHub: kadler).

---

FYI, I improved the iDB2Call transport in bacc741 to support passing a PEP-249 compliant driver. Theoretically you could implement XMLSERVICE in any DBMS and it would work, thus the "iDB2Call" name is a misnomer and ideally would be fixed. Along with that change, I'd propose fixing #1 and just have a "DatabaseCall" or similar name. Leave modules with the old names that merely load and re-export the ones in the right location.

[jkyeung]

Original report by John Yeung (Bitbucket: jky, GitHub: jky).

Actually, I'm @jkyeung on GitHub. (I couldn't get jky on GitHub, and that link takes you to someone else.)

[kadler]

Oh no! I wonder if I can re-do the migration script.

[kadler]

Nope, it's not possible it seems unless we delete the repository and start over:

https://github.com/jeffwidman/bitbucket-issue-migration#additional-notes

This script is not idempotent--re-running it will leave the first set of imported issues intact, and then create a duplicate set of imported issues after the first set. If you want to re-run the import, it's best to delete your GitHub repo and start over so that the GitHub issue IDs start from 1.

[kadler]

With #18 you can now do:

import pyodbc
from itoolkit.transport import DatabaseTransport

conn = pyodbc.connect("DSN=mydsn")
transport = DatabaseTransport(conn)

[jkyeung]

Nope, it's not possible it seems unless we delete the repository and start over:

No, don't bother. It sounds like you weren't going to anyway, but just to make it clear, I don't think it's worth the trouble.