Code

Opened 9 years ago

Closed 9 years ago

#4 closed enhancement (duplicate)

Add a db cache backend

Reported by: adrian Owned by: jacob
Component: Core (Cache system) Version:
Severity: normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

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

Attachments (0)

Change History (5)

comment:1 Changed 9 years ago by wgunadi@…

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.

comment:2 Changed 9 years ago by jacob

  • milestone set to Version 1.0

comment:3 Changed 9 years ago by adrian

  • milestone Version 1.0 deleted

comment:4 Changed 9 years ago by Simon Willison

Ticket #515 contains a patch for this.

comment:5 Changed 9 years ago by Simon Willison

  • Resolution set to duplicate
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.