Hi, >take a look at the current implementation. we are doing this part >already, we're using inspect to look at kwargs. its not fragile at >all. so im just proposing we add extra sniffing of dbapi.connect(), >and that we also look in the query string for the full range of those >parameters. this will allow 90% of what people want to pass to be >allowed within the URI. > > Having kicked off this thread, I think my take now is to keep things more-or-less as they are - from all the points people have made, it's clear major changes will be more painful that it's worth.
Having DefaultEngineStrategy.create pass the URI to the dialect's constructor would be great - that would let MSSQL have the module_name as a URI parameter. Just this change would statisfy my needs. Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
