try out this patch against trunk:
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
fully_qualified_columns.patch
Description: Binary data
I would have to carefully test this patch against all dialects we have which support schemas, like PG and such, in order to commit it. For example its also putting the schema name into UPDATE/INSERT etc. and I'd have to ensure that all DB's are OK with that (which they should be, of course). It also modifies the labeling to produce "schema_table_colname". Long label names, which oracle is particularly sensitive to, should get truncated . On Mar 25, 2008, at 4:23 PM, vkuznet wrote: > > Yes, the team is forced to use schema namespace everywhere and once > schema will be deployed, the queries without schema namespace will not > run at all. > > --~--~---------~--~----~------------~-------~--~----~ > 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 > -~----------~----~----~----~------~----~------~--~--- >
