- changed milestone to 0.3.0
With MS SQL Server 2005 database created as case sensitive, sqlalchemy fails to access information schema
The module now uppercases all table and column names when accessing the INFORMATION_SCHEMA views. Tested on both case-sensitive and case-insensitive databases.
Comments (10)
-
repo owner -
repo owner - assigned issue to
-
Account Deleted (original author: ram) I'll take it...I believe I've got an installed version of 2005 around that I can create a case-sensitive DB on...
-
Account Deleted - changed status to resolved
(original author: ram) None
-
Account Deleted - attached mssql.patch
Patch of mssql.py against r1897
-
Account Deleted - removed status
- changed status to open
Thanks very very much for making this work: it was a major stumbling block, and I was scratching my head over how much code I'd have to change to patch it. I've added a patch against mssql.py@9a36771499c1428ab64af4a17cbbb83e54b4e85a to cover a few typos which slipped past the testing. Patched here at home (where I don't have MSSQL) altho' tested earlier at work where I do.
-
Account Deleted (original author: ram) Applied, thanks
-
Account Deleted OK, looks like it got fixed anyway in f6594a32dceae2755331c1ae678cc5ea09058767.
-
Account Deleted - changed status to resolved
(original author: ram) None
-
repo owner - removed milestone
Removing milestone: 0.3.0 (automated comment)
- Log in to comment