Brad Clements wrote:
Michael Bayer wrote:
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
Well, maybe I'm giving the correct answer to the wrong question here,
but I can claim lack of caffeine:
def filter_app_factory(application, global_conf, dburi, **kw):
global_connect(dburi, **kw)
return application
[filter:database]
use = egg:Blossoms#database
dburi = postgres:///lbruno
module = psycopg1
[app:whatevah]
use = egg:Blossoms
root = mygreat.package.namespace
filter-with = database
So, have I missed anything right under my nose? I'll be claiming lack
of caffeine in advance.
--
Luís "LOCIA! What a nice acronym!" Bruno
-------------------------------------------------------
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&kid7521&bid$8729&dat1642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
