On Mon, May 18, 2009 at 09:11:29PM +0200, Piotr Ożarowski wrote: > [Geoff Crompton, 2009-04-28]
>> When trying to autoload a table on a remote mssql server, sqlalchemy >> crashes. >> This may be related to http://www.sqlalchemy.org/trac/ticket/1312. > please check 0.5.4p1-1 (I just uploaded it to unstable). I think > this new upstream release fixes your problem (ticket 1405 is now > closed, 1312 is still open, though). I don't have access to mssql, > so I cannot really check it. Upstream #1312 has been closed for 0.6, so it is plausible this is has been solved in Debian for ages (before oldoldstable)? Anyway, I cannot reproduce with python3-sqlalchemy 1.3.22+ds1-1 python3-pymssql 2.2.2-1+b3 libsybdb5 1.3.17+ds-2 note that I use as connection URL: 'mssql+pymssql://%s:%s@%s/%s' if I use 'mssql://%s:%s@%s/%s' then sqlalchemy tries to use PyODBC, which doesn't seem to be what the original bug reporter was using.
