Jeremy Self

vishen is correct, database views are updated outside of django so we can't really know inside of django (or johnny-cache) if a base table is invalidated that is used in...

This should have been fixed in the pull request #34. Can you let us know if you're still running into this using the git version of johnny cache? We're waiting...

You added the LocalStoreClearMiddleware? That's the only thing that I can think of that would cause an app server to increase in memory footprint via johnny cache (that or a...

Yes, it's a good idea to because columns may still be missing/etc, or any migrations that have happened won't appear in the cached version until a table write.

No, since we invalidate the entire table on any write (hence you essentially get a cold cache every table write), there's not much point since previous generations don't need to...

Thanks @linlinzhouchen, but that's the opposite of running a task as a non-root user. That's running the task as a sudo'd root user.

Hello, If you enable the cache (and never disable it), then really the enable at the top should be enough. That's not always possible though if you need to run...

Working on it this weekend, we have about 20 failing tests so there's a lot of new issues with 1.6, particularly around transaction management, so it may be a bit.

There's been fixes to branch django-1.6 that brings the test failures to about 3, all transaction based. I haven't had a chance to revisit it though, or to test multi-db....

Thanks for the submission, most likely we'll be going through all of the bugs again with django 1.5 (and since it involves a bunch of queryset changes, we may have...