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. -- 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.
