Opened 20 years ago
Closed 19 years ago
#4 closed enhancement (duplicate)
Add a db cache backend
| Reported by: | Adrian Holovaty | 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.
Change History (5)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| milestone: | → Version 1.0 |
|---|
comment:3 by , 20 years ago
| milestone: | Version 1.0 |
|---|
comment:5 by , 19 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.