Changes between Version 3 and Version 4 of DistributedTrac

Timestamp:

Jan 10, 2010, 8:41:45 PM (14 years ago)

Author:

Jürgen A. Erhard <jae+trac@…>

Comment:

—

DistributedTrac

@@ -19 +19 @@
   * The trac server could create a temporary database from the versioned data. An SQLite memory db could work well for this.
    * It would be really slick if it could recognize when the data has changed and just update an existing import instead of redoing the entire set.
+   * Isn't it obvious?  Trac would still use a DB, only it wouldn't be the canonical source of info.  That would be that repository data.  The DB (and no, not in-memory, at least not default, depending on size of repo/mem of server machine) would be a kinda cache.
  * Trac data commits could clutter the VCS log making it difficult to find the important code changes amongst many revisions of "Page X changed by Y".
    '' That's probably the most visible reason about why it's not such a good idea to use the same repository for Trac itself. See the more in-depth discussion of this aspect in TighterSubversionIntegration. Nevertheless, as Trac makes progresses added MultipleRepositorySupport, it wouldn't be such a big deal to use a dedicated repository. -- cboos''