On May 25, 2010, at 12:20 PM, Daniel Mostovoy wrote: > > That's what I thought... but in that case a table created with upper case > column names should not be accessible by the lower case column name... right? > I found that the opposite was true using oracle... that a table created using > uppercase column names was actually not accessible using the UPPERCASE name. > Here's an example to illustrate...
Oracle's native "case insensitive" style is to use ALL_UPPERCASE names. When using SQLAlchemy you should not be concerned with this, as that conversion is handled internally. You still need to use all lower case names to indicate a case insensitive name (fyi this applies to table names too). Use all lower case in SQLA constructs, ensure that the tables were created either with the SQLA case-insensitive constructs or otherwise without using quotes, and your problems will go away*. * In the case that your tables were created in Oracle using quotes, i.e. 'create table "THIS_IS_REALLY_UPPERCASE"', then they'd have been created as case sensitive. This might have happened if you used your case sensitive Table constructs to issue CREATE TABLE. I'd suggest you drop those tables and start over again with an all-case-insensitive setup if at all possible. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
