On Sun, Oct 16, 2011 at 12:45 PM, Alexander Schepanovski <[email protected]> wrote: > As one of the authors of multiple third-party packages I can say that > though it is not too hard still integrating cache into ORM have some > problems. There are several approaches: > > 1. Custom Manager and QuerySet subclasses (cachebot, cache-machine). > The clearest one and lest powerful - can't use with contrib and third- > party modules without their modification or monkey patching. Also, it > conflicts with other custom Managers and QuerySets. > > 2. Monkey patching Django ORM (johnny-cache, cacheops). Probably > simplest to use, not so simple to maintain. > > 3. Model subclass with ModelBase metasubclass (orm-cache). Has same > problems as 1 and more. > > The situation now as with using external templates prior to django > 1.2.
We're open to suggestions. As I've said previously in this thread, I'm not convinced there is a single solution we can implement as part of core. However, if there is some API that we can expose, or an interface we can formalize, that will make adding query caching easier, we're open to suggestions. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
