On Jul 7, 8:52 am, Paul Johnston <[EMAIL PROTECTED]> wrote:
> Hi,
>
> There is a degree of overlap between options you pass to create_engine,
> and parameters in the DB URI. How about merging these concepts? Perhaps
> DefaultEngineStrategy.create could parse the URI for paramters, possibly
> do some type coercion, and update kwargs with any parameters. Individual
> dialects could take everything as parameters to the constructor, rather
> than doing URI parsing in create_connect_args.
do you mean, the URI would have args that are used by the DBAPI *or*
the dialect ? right now, all query strings in the URI go to the
DBAPI's connect() method. mixing them up I fear opens the door for
name conflicts. what if some DBAPI were suddenly supported that had a
connect() argument called "echo" ?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
