Would it be possible (and beneficial) to have a Table use a globally
defined ProxyEngine located within sqlalchemy if none is specified
when you create it?
I ran into this when I was trying to incorporate sqlalchemy into two
different projects that run in the same process, but don't
necessarily know about one another. I solved this by having a third,
common place to store the single proxy engine, and have both
reference it, but I wasn't happy with this solution. If there was a
global or 'built-in' ProxyEngine, you wouldn't have to deal with the
creation or management of the ProxyEngine for many simple cases. You
would of course still be able to assign engines at instantiation time
or reassign them at runtime, but it may simplify things, if you don't
have to keep track of a ProxyEngine if you don't need to.
I have been using sqlalchemy for only a short time, but I have been
really pleased with how expressive and complete the API is, how great
the documentation is, and how much continued development is going
into it!
Ex.
user_table = Table('user',Column(...), Column(...),...)
sqlalchemy.default_engine.connect('postgres://...')
sqlalchemy.default_engine.begin()
# ... do various things
sqlalchemy.default_engine.commit()
Aaron
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
