Django

Code

Ticket #4 (closed: duplicate)

Opened 3 years ago

Last modified 1 year ago

Add a db cache backend

Reported by: adrian Assigned to: jacob
Milestone: Component: Cache system
Version: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

We should have a db cache backend -- this will be very useful for people who can't/won't run memcached.

Attachments

Change History

07/28/05 11:11:29 changed by wgunadi@nextcoder.net

Need to be careful with this, my current client has a requirement to share a single database across multiple servers. I'm sure they are not the only one with this kind of requirement. In this case, a database cache (I'm assuming you're talking about read *and* write cache) can make it difficult to synchronize among servers. At least the cache feature should be optional.

08/01/05 14:59:16 changed by jacob

  • milestone set to Version 1.0.

08/17/05 17:14:45 changed by adrian

  • milestone deleted.

09/16/05 06:28:17 changed by Simon Willison

Ticket #515 contains a patch for this.

09/16/05 12:01:24 changed by Simon Willison

  • status changed from new to closed.
  • resolution set to duplicate.

Add/Change #4 (Add a db cache backend)




Change Properties
Action