Changes between Version 8 and Version 9 of DatabaseBackend
- Timestamp:
- May 23, 2005, 4:05:21 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DatabaseBackend
v8 v9 33 33 == Store Tickets and Wiki pages directly in the Subversion repository == 34 34 35 A compelling idea with many : see a more complete discussion in TighterSubversionIntegration35 A compelling idea with many advantages: see a more complete discussion in TighterSubversionIntegration 36 36 37 37 === Pros === 38 38 39 ( taken from [http://subissue.tigris.org/ Subissue], a project that aims to implement such a solution)39 (some taken from [http://subissue.tigris.org/ Subissue], a project that aims to implement such a solution) 40 40 41 41 * "Issues are stored directly in your Subversion repository, next to your source — right where they belong!" i.e. you have access to your issues and project documentation (wiki) by just checking out your source. 42 42 * no extra RDBMS required; Subversion already has its own database. 43 43 * "logging, intelligent reporting, history, and access control straight out of the box: most everything required for issue tracking is already in place — right down to email notification." 44 * Trac currently mixes transient and non-transient data in a single database. By storing all valuable data (which cannot be reconstructed by resynching with the repository) in a version controlled data store would help separating both sorts of data and minimize the amount of data that needs to be backed up. 44 45 45 46 === Cons === 46 47 47 * no SQL 48 * no SQL -- ''There is no reason why Trac might not store "transient" data in a regular database. Such database would be required anyway, because some features of Trac need indexing for fast searching.'' 48 49 * (from [http://projects.edgewall.com/trac/ticket/411#change_3 411]) revision numbers of the repository would climb like crazy because every ticket added or edited would create a new changeset -- ''but a different, dedicated, repository could be used instead the one being Trac'ed'' 49 * (from [http://projects.edgewall.com/trac/ticket/411#change_3 411]) trac currently does not modify the repository at all -- changing it to do so might create other problems -- '' which ones?''50 * (from [http://projects.edgewall.com/trac/ticket/411#change_3 411]) trac currently does not modify the repository at all -- changing it to do so might create other problems -- ''If this really is an issue, this could also easily be solved by using a different repository for storing issues and wiki pages.'' 50 51 51 There seem to be more cons :( - the Subissue project [http://svn.haxx.se/tsvn/archive-2004-08/0473.shtml seems to be dead]. 52 There seem to be more cons :( - the Subissue project [http://svn.haxx.se/tsvn/archive-2004-08/0473.shtml seems to be dead]. ''There are especially no cons without remedy. There are more dead projects than alive ones -- this is no reason for not implementing '''the''' feature that eveybody first thinks of after downloading Trac...'' 52 53 53 54 See also [http://lists.edgewall.com/archive/trac/2004-August/#594 <Trac> Why does Trac use SQLite for Wiki?]
