On Thu, May 30, 2013 at 4:19 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: >> In case I'm not clear, this would not be cached if I were to take >> id(internals) >> >> query(Blah).filter(blah).join(blah).first() >> >> But I don't care, because that's "expensive" on its own. > > result caching (because we're calling first()) is a whole different thing. > the dogpile.cache recipe addresses that - its a widely used recipe and sure, > that would make a great feature too, I keep it as a recipe so that people who > use it have spent time understanding it.
Oh no, I was referring to the query not the result. Results will never be cached with what I propose. -- 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.
