On Jul 8, 2007, at 11:04 AM, Rick Morrison wrote:
> How about a simple scheme in which options meant for engine or > dialect are prefixed with a tag that would differentiate them from > other options that would be passed through to the DBAPI? Something > like "sa-echo" or similar. Any other ideas? > thats ugly to me. if you know your DBAPI uses a certain argument, you should be able to just pass it through. similarly i dont want SA's args with some ugly prefix. prefixing is just a hack for something this fundamental. i would vote just for the each dialect making the decision as to what arguments get interpreted how from the query string, it can do wahtever it wants, end of story. also, the DefaultEngineStrategy would pass the URI to the Dialect's constructor, and when it calls for the "connect args", they are statefully set within the Dialect based on the URI in the constructor; i.e. the get_connect_args() method now takes no arguments. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
