Qvx wrote:
"global" part from global_connect name just raised an alarm signal
inside my
head. If I'm reading you correct, global_connect will make it
impossible to
use more than one database. I hope I'm missing something obvious.
What is wrong with __engine__ module variable?
If it is possible to still connect to different database per python
module
then I guess I'm OK with global_connect. Just give me a recipe how to
connect to different database in each module and I'll be happy.
I dislike having ActiveMapper have its own ProxyEngine when
SQLAlchemy has a globally defined ProxyEngine called the "default
engine" that can be accessed as: sqlalchemy.schema.default_engine.
You should be able to get the functionality you need simply by
creating your engines and doing the appropriate dance with the
default ProxyEngine in your modules.
--
Jonathan LaCour
http://cleverdevil.org
------------------------------------------------------------------------
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
