On Jul 10, 2006, at 2:58 PM, dmiller wrote: > However, in the original case that brought this up I would argue > that the Objectstore class should not extend SessionContext. > Otherwise it superimposes the interface for the session context > with that of the current session. That will tempt developers to > check a session instance for a "current" property thinking they can > treat it like an session context. That's bad--if some function > needs a SessionContext instance then it should require that > interface only. If it needs a Session instance then it should > require that interface. But it should not ask for a Session and > then try to treat it like a SessionContext or visa-versa. If > someone really needs a single object that is both a SessionContext > and a Session at the same time then they can create their own > object that proxies both or whatever...but we shouldn't encourage > that.
it doesnt matter much to me, i am just trying to go in the direction of "no new bugs" as much as possible at this point in 0.2..so i was preferring less change over greater change. ------------------------------------------------------------------------- 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 Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
