> how about 'contextualsession' or something....I really dislike the > name "contextsession".
__session__ would probably be fine, unless you're afraid to conflict with something else. We use __int__ to get ints out of an object, __nonzero__ to get a boolean, and so on. Using __session__ looks like a reasonable way to get a session out of an object. > also i dont understand how sticking a __call__() on SessionContext > would have any impact on its existing get/set/del operations. Daniel was probably talking about SessionContext.current. It may be nice, but I don't think this interface should be *enforced* anywhere by SA (and I don't think Daniel is suggesting it either). I'd also like to see instances being queried for sessions. Daniel's implementation of current_session(obj) is currently doing lookups on classes only. I've provided one potential implementation in a message of this thread. -- Gustavo Niemeyer http://niemeyer.net ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
