Hi, That looks like a bug to me. As Rick suggested, first try with the latest svn version. If it's still broken (I expect it will be), create a minimal test case and file a bug on the tracker.
You've got an obvious workaround of specifying the schema on your tables. Actually, I'm not quite sure why MSSQL has created a db-specific idea of a default schema - this just seems to be inviting trouble. Paul metaperl wrote: >to me this implies that setting the default schema name on the engine >does not make the proper schema qualifications on the SQL... > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
