Aaron Bickell wrote:
user_table = Table('user',Column(...), Column(...),...)sqlalchemy.default_engine.connect('postgres://...') sqlalchemy.default_engine.begin() # ... do various things sqlalchemy.default_engine.commit()
I love this idea, personally. But Aaron is a co-worker of mine, so I am biased I suppose.
I always found it kind of strange to have to pass in an engine when I am defining a table. At that point, I really have no idea what engine I am going to be using, or the DB connect string. The ProxyEngine helps this greatly, but it does seem kind of strange to have to pass it into the constructor for every table, and store it in my own global place.
In short, I am in full-support of this concept, at least in principle. -- Jonathan LaCour http://cleverdevil.org ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
