uniform interface for MySQL & MSSQL

Gerhard Häring gerhard.haering at gmx.de
Tue Jul 16 04:07:54 EDT 2002


* Johann <observer at NOSPAM.space.pl> [2002-07-16 09:31 +0200]:
> On Mon, 15 Jul 2002 19:38:28 GMT, Alex Martelli <aleax at aleax.it>
> wrote:
> 
> >Have you tried:
> >http://www.object-craft.com.au/projects/mssql/
> 
> It does not work. I tried to compile it under Cygwin but some files
> (*.h) are missing :-(
> 
> In file included from mssqldb.c:25:
> mssqldb.h:37: sybfront.h: No such file or directory
> mssqldb.h:38: sybdb.h: No such file or directory
> error: command 'gcc' failed with exit status 1
> 
> I found this module have no cursor.seek(nr) method. :(

It's probably not difficult to implement. I planned to suggest you use
mxODBC, as this is a commercially supported module and does support both
databases. Then I discovered that it doesn't currently support
cursor.seek either, and asked on the DB-SIG mailing list. Marc-Andre
Lemburg, its author, said that mxODBC 2.1 will support most of the
optional DB-API extensions of PEP 0249, which includes cursor.seek. You
might want to ask him if he'll support cursor.seek and if this will work
with both MS SQL and MySQL.

Gerhard
-- 
mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))





More information about the Python-list mailing list