[sqlalchemy] Re: Uppercase column names in table.insert({ })

On Mon, Sep 29, 2008 at 4:46 PM, Itamar Ravid [EMAIL PROTECTED] wrote: Thanks for the answer, Mike. I was used to Oracle's behavior while writing raw SQL, in which the case of unquoted column identifiers doesn't matter. This behavior seems reasonable enough, although the inconsistency between

[sqlalchemy] Re: Uppercase column names in table.insert({ })

On Oct 1, 2008, at 10:03 AM, Gaetan de Menten wrote: On Mon, Sep 29, 2008 at 4:46 PM, Itamar Ravid [EMAIL PROTECTED] wrote: Thanks for the answer, Mike. I was used to Oracle's behavior while writing raw SQL, in which the case of unquoted column identifiers doesn't matter. This

[sqlalchemy] Re: Uppercase column names in table.insert({ })

This is the expected behavior. SQLA operates in a case sensitive fashion whenever a table or column identifier is given in mixed case or upper case. Use all lower case for case insensitive. Since SQLA seeks to provide a database-agnostic API to the backend, this includes Oracle as

[sqlalchemy] Re: Uppercase column names in table.insert({ })

Thanks for the answer, Mike. I was used to Oracle's behavior while writing raw SQL, in which the case of unquoted column identifiers doesn't matter. This behavior seems reasonable enough, although the inconsistency between the cursor description and SQLA's column identifiers could throw some