Hi Michael, Am Montag, den 22.11.2010, 11:18 -0500 schrieb Michael Bayer: > > Originally I added only 2 fields and 4 methods to the Session but it > > seems like this will grow a bit. Is it okay to add a whole bunch of > > methods to my Session class? Any hints how to avoid name clashes for > > future SQLAlchemy versions? > > yeah there's no magic bullet here, you can add as many methods as you like > and each one raises the chance of a future collision by a tiny amount. We > don't add too many methods to Session so its not terribly dangerous, but you > could consider building a Session facade of your own which delegates to the > "real" Session internally. If I were really adding a comprehensive > business-centric persistence layer I'd almost certainly do that.
I originally had such a facade, but I dumped it because I did not want to reimplement the scoped session adapter. Any hints how to get the best of both worlds? ;-) Thanks, Torsten -- DYNAmore Gesellschaft fuer Ingenieurdienstleistungen mbH Torsten Landschoff Office Dresden Tel: +49-(0)351-4519587 Fax: +49-(0)351-4519561 mailto:torsten.landsch...@dynamore.de http://www.dynamore.de Registration court: Mannheim, HRB: 109659, based in Karlsruhe, Managing director: Prof. Dr. K. Schweizerhof, Dipl.-Math. U. Franz -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
