Hello Michael, (...) > theres more you can do..the Session can bind different tables to > different engines, it can bind to Connections instead of Engines, and > the Session can provide a real transactional interface too. whats > missing is, the docs, and also some convention on how these patterns > will be most expediently used.
It sounds like nice stuff is coming! Have you had a chance to look at the message I've sent regarding the clustering scheme? Do you think something about the details I've explained could be considered in these changes or would it be too incompatible with the changes you're doing? > keep in mind though that the old way of doing things is still pretty > much intact, and the docs will more often than not refer to the > "thread-local" way of doing things. Fair enough.. > with all of this , SA will become more viable as a set of tools with > which to build database frameworks on top of (and probably even more > daunting to newcomers....). I belive that if the framework is well thought and well built, people will happily wrap it into simple ways for those who need just the basic things. In fact, this is already happening [1]. [1] http://spyced.blogspot.com/2006/04/introducing-sqlsoup.html -- Gustavo Niemeyer http://niemeyer.net ------------------------------------------------------- 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
