mmalone's django-caching. Mike Malone shares code used by Pownce to add QuerySet level caching to Django. It’s a smart implementation—a CachingQuerySet class inspects the arguments passed to get(), and if they’re just a straight forward exact PK lookup hits memcache for the object before hitting the database. Signals are used to invalidate the cache.
Sign in with 
OpenID
What is it with projects on Guthub that they all seem documentation-free?
Andy Baker - 7th May 2009 11:49 - #
I think it's more that GitHub makes it ridiculously easy to dump small bits and pieces of code - in this case, it was just some code to illustrate concepts from Mike's talk at EuroDjangoCon - not really meant to be used as a stand alone project, more of an example of how something can be done.
OK. That was probably a bit snarky of me when someone is being generous with their time and code.
I quite miss the clean layout of Google Code and am having one of those 'so we are all moving to Github, are we? No-one told me!' kind of moments...
Andy Baker - 8th May 2009 14:45 - #
GitHub is more useful than Google Code from a collaboration point of view for a couple of reasons. Firstly, I can follow people and projects and see a combined news feed of changes to them. Secondly, if I publish code there someone can fork it (without my permission), make a change and then I can merge their changes back in to mine by clicking a button on a web page.
I experienced some problems in admin site when I tried to use django-caching. ( TypeError: can't pickle instancemethod objects ) when tried to view cached model record.
See http://paste.pocoo.org/show/119491/
Nick - 28th May 2009 02:52 - #