#1132: Use Subversion for data repository
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: cboos
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: wiki | Version: none
Severity: normal | Resolution:
Keywords: objectstore |
------------------------------+---------------------------------------------
Comment (by cboos):
Here's how I see it (roughly):
* A pluggable storage backend for the Trac objects (content, properties),
which will be able to do the versioning.
That backend could be the DB as usual, but also any other repository
backend. A simple FS backend could be possible too...
* A database cache for the latest values (queries, full text search).
Maybe even some kind of history, too (property changes?).
* A filesystem cache for the attachements (when we need to do a
send_file)
and possibly other generated data.
The data stored in the last two components could always be rebuilt
from the authoritative information in the storage backend.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1132>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
