[Sqlalchemy-tickets] [sqlalchemy] #1231: Case-sensitive problems in the mapper
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2008-11-24 19:26:32
|
#1231: Case-sensitive problems in the mapper ------------------------------------------------------------------------+--- Reporter: guest | Owner: zzzeek Type: defect | Status: new Priority: medium | Milestone: Component: (none) | Severity: no triage selected yet Keywords: case,sensitive,insensitive,case-sensitive,case-insensitive | Status_field: awaiting triage ------------------------------------------------------------------------+--- When using sqlalchemy 4.7.1 with oracle 9, I have encountered the following problem: Problem: When I defined table names, or column names in upper case, and not in lower case, I suffered from a very strange behaviour, although the db is not case sensitive. Case scenario: I defined my tables using the mapper. All the tables were defined in upper case. But none of my foreign keys works. sqlalchemy threw an exception that I must explicitly write the primary join expression. After I wrote the primary join condition, it worked fine. Yet, this solution didn't please me. I found out that when I define all the "id" columns explicitly (with autoload = True), it works fine without needing the join condition. I defined them also with upper case. But then, all sort of weird things happened. Only then I found out that all the tables that I defined their columns have two columns for the id - one in upper case and one in lower case. And then I thought to myself, that maybe I should define the table also with lower case. So I did it, and from then on, I didn't have to define the "id" columns explicitly. Connected to ticket:487. Reported by Kobi Perl. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1231> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |