With MS SQL Server 2005 database created as case sensitive, sqlalchemy fails to access information schema

zzzeek / sqla_issue_test

1 stars 0 forks source link

With MS SQL Server 2005 database created as case sensitive, sqlalchemy fails to access information schema #261

Closed zzzeek closed 6 years ago

zzzeek commented 18 years ago

Originally reported by: Anonymous

The module now uppercases all table and column names when accessing the INFORMATION_SCHEMA views. Tested on both case-sensitive and case-insensitive databases.

Bitbucket: https://bitbucket.org/zzzeek/sqlalchemy/issue/261

zzzeek commented 10 years ago

Original comment by Michael Bayer (Bitbucket: zzzeek, GitHub: zzzeek):

Removing milestone: 0.3.0 (automated comment)

zzzeek commented 18 years ago

Original comment by Anonymous:

(original author: ram) None

zzzeek commented 18 years ago

Original comment by Anonymous:

OK, looks like it got fixed anyway in f6594a32dceae2755331c1ae678cc5ea09058767.

zzzeek commented 18 years ago

Original comment by Anonymous:

(original author: ram) Applied, thanks

zzzeek commented 18 years ago

Original comment by Anonymous:

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.

zzzeek commented 18 years ago

Original comment by Anonymous:

Patch of mssql.py against r1897

zzzeek commented 18 years ago

Original comment by Anonymous:

(original author: ram) None

zzzeek commented 18 years ago

Original comment by Anonymous:

(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...