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

Issue #261 resolved

Former user created an issue 2006-08-01

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

mssql.patch

Comments (10)

Mike Bayer repo owner
- changed milestone to 0.3.0
- 2006-08-11T17:46:14+00:00
Mike Bayer repo owner
- assigned issue to
- 2006-08-11T17:46:14+00:00
Former user 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...
- 2006-08-12T23:35:10+00:00
Former user Account Deleted
- changed status to resolved
(original author: ram) None
- 2006-09-24T00:01:54+00:00
Former user Account Deleted
- attached mssql.patch
Patch of mssql.py against r1897
- 2006-09-25T14:41:50+00:00
Former user 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.
- 2006-09-25T14:43:30+00:00
Former user Account Deleted
(original author: ram) Applied, thanks
- 2006-09-26T10:37:59+00:00
Former user Account Deleted
OK, looks like it got fixed anyway in f6594a32dceae2755331c1ae678cc5ea09058767.
- 2006-09-28T06:55:50+00:00
Former user Account Deleted
- changed status to resolved
(original author: ram) None
- 2006-09-29T13:04:09+00:00
Mike Bayer repo owner
- removed milestone
Removing milestone: 0.3.0 (automated comment)
- 2014-02-23T18:12:52+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: resolved

Component: (none)

Milestone: –

Votes: 0

Watchers: 0