Hi, I'm looking why the unittest SchemaTest.test_create_with_defaultschema does not pass with MS-SQL.
The reason is that MSSQLDialect.get_default_schema_name takes no argument, while the unittext gives it an engine. The Mssql dialect, for example, does take an argument. Having a closer look at MSSQLDialect.get_default_schema_name, it simply returns self.schema_name, which is initialised in __init__ with the value "dbo". This is were I don't know what to think. Isn't the default schema depending on the connection ? If so why is it initialized to "dbo" ? Another strange thing : MSSQLDialect defines a set_default_schema_name, and it's the only dialect to do that. Before patching this in the wrong way, I'd like to have a little bit more details on how the default_shema stuffs are supposed to work. Sub-question : shouldn't the set_default_schema_name issue a "USE <name>" ? Last thing : could someone tell me if the patches I posted for mssql looks 'commitable', because I'd prefer fixing those if needed before continuing my failing unit-tests slow (one per day) review. Thanks, Christophe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
