On Apr 6, 2006, at 6:21 PM, Robert Leftwich wrote:
It seems to me that in the near future the notion of Table.toengine
() is going to disappear or at least become redundant. What impact
is that likely to have on the people, like me (the only one?), who
are using that functionality heavily?
Robert -
i am sticking with the capability for SchemaItems and ClauseElements
to be "bound" to engines. the binding will become a clearer concept
and will be optional in all cases. the toengine() will still be
there. the item can either be bound to an engine at creation time,
or one can be provided at execution time. the "engine" itself can be
an application-scoped SQLEngine, or ConnectionProxy which is bound to
a particular connection/tranasction resource. the Session will also
gain the ability to bind arbitrary things to engines.
also while it sounds like a lot i think it will ultimately be easier
to use and understand.
- mike
-------------------------------------------------------
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
