On Mon, Jun 3, 2013 at 1:55 AM, Michael Bayer <mike...@zzzcomputing.com>wrote:
> Well, if that works, it certainly covers my needs so there would be no > pressing need to incorporate it into the core. > I'll let you know tomorrow. > > > > It's so straightforward at this point I'm leaning towards some more > cleanup and adding to 0.9. I'll probably cache the compiled statements on > the QueryContext itself too, and the cache dictionary will be via Session / > Sessionmaker. > Bear in mind that the use case I'm not only now, but always facing, involves queries in many, different, short-lived sessions. So making it Session-local won't live long enough, unless it can be given to the Sessionmaker itself and have that caching context be shared among all sessions. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
