On 30 May 2006 at 16:30, Michael Bayer wrote: > usually additional params that are specific to a certain database > implementation are passed through as keyword arguments to > create_engine(): > > this keeps the URLs completely consistent and provides a nice > separation of "db-specific" vs. "db-agnostic".
Yeah, but then there's no way I can use sqlalchemy in a generic and non- database specific way via WSGI using PasteDeploy, I'd be forced to write app middleware specific to the database that was being used. besides, I'm pretty sure that in 0.1 this used to work.. back when engines parsed their own "urls".. will you accept a patch to allow ?arg=value in url? -- Brad Clements, [EMAIL PROTECTED] (315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
