On Apr 6, 2006, at 3:11 PM, Michael Bayer wrote:
hey dan -
to give you an idea, check out http://www.sqlalchemy.org/trac/
changeset/1262
if you check that one out i think your lazyloader issue should be
resolved (added a unit test for that).
the next phase would be the using() method gives you a proxying
object that just adds the "session" keyword argument as
appropriate. and then maybe doing something similar with an
"engine" keyword argument. then maybe some cleanup of mapper
method signatures and we're just about there with sessions/engines
totally per-call. As "engine" is already a keyword argument to
most of the SQL construction objects, and Ive removed the "type"
dependency yesterday, I think itll be quite easy to create and use
Table objects with an engine of "None" in the very near future.
fortunately, its all Python....none of this is very hard....
Does this mean I don't need to use mapper.using(...).select(...) to
execute a query on a session anymore? i.e. I could do mapper.select
(session=x, ...)
~ Daniel
-------------------------------------------------------
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
