On Apr 16, 1:23 pm, "Dr.T" <[EMAIL PROTECTED]> wrote:
> Perhaps a line could be added to the Table constructor documentation
> to point out that the "name" kwarg is ignored when the table name is
> in mixed case (because this is not obvious)?
I think you mean the "quote" kwarg.
I also agree that this is misleading.
I would also like to mention that I have run into a similar mixed-case
problem, and if the quote= argument was used for Oracle and PostgreSQL
table names, it would resolve my problem.
The problem is that I'm working with a schema that was created through
manual sql scripts that have mixed case:
CREATE TABLE MyTable (...)
In Oracle, this creates MYTABLE. In PostgreSQL, this creates
mytable. In MSSQL, this creates MyTable.
Because of this discrepancy, it's impossible to create a SQLAlchemy
model that works with all three databases. Michael's suggestion to
"use all lowercase" only works for PostgreSQL/Oracle, but breaks in
MSSQL. When I noticed the quote= parameter, this seems to effectively
indicate to SQLAlchemy the syntax that was used to create the database
(in particular, the table names aren't quoted).
This is related to Ticket #1012 (http://www.sqlalchemy.org/trac/ticket/
1012), which describes the symptom encountered in the MSSQL case.
This is an ongoing issue for me. Any suggestions are appreciated.
Regards,
Jason
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
