On May 31, 2012, at 10:35 AM, Claudio Freire wrote: > On Thu, May 31, 2012 at 12:50 AM, Michael Bayer > <mike...@zzzcomputing.com> wrote: >>> >>> Thing is, in order to work with a large volume of objects, you're >>> forced to do this, otherwise the session can grow uncontrollably. >> >> flush periodically, and don't maintain references to things you're done >> with. The Session does not strongly reference objects that have no pending >> changes, and they'll be garbage collected. > > Problem is, I'm stuck with strongly-referencing sessions. The app > comes from SA 0.3, and is heavily relying on the session as a kind of > L1 cache - removing that assumption is a really huge task we haven't > gotten to. We managed to upgrade it to SA 0.5, but we kept > strongly-referencing sessions.
well you'd really need to change that, sorry. I get very close to removing the strongidentity map on each release, you're the first user I've ever encountered with a dependency on it... -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@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.
