Edgewall Software

Changes between Version 6 and Version 7 of DatabaseBackend


Ignore:
Timestamp:
Jan 31, 2005, 1:25:24 AM (19 years ago)
Author:
ryandesign
Comment:

corrected typos, and reworded an unclear sentence

Legend:

Unmodified
Added
Removed
Modified

  • DatabaseBackend

    v6 v7  
    33Currently, Trac uses [http://www.sqlite.org SQLite] as its database backend.
    44
    5 However, there has been several requests that other databases should be supported as well (see #126).
     5However, there have been several requests that other databases should be supported as well (see #126).
    66
    77== Existing Proposals and Implementations ==
    … …  
    1414  If SQLObject (see below) works well, this proposal may not be necessary, but I would like some feedback (brad at dsource dot org) on the following proposal:  [http://trac.dsource.org/projects/test/wiki/TracTicketDataModelChanges TracTicketDataModelChanges]
    1515
    16   I like its elegance in handling custom fields, allowing multiple ticket attributes per ticket (i.e. this is a problem in 0.7.1, 0.8, and 0.9, so ticket gets multiple versions marked on it), and I imagine it results in reduced code overall for the app, because of the use of metadata.
     16  I like its elegance in handling custom fields, allowing multiple ticket attributes per ticket (i.e. the ability to indicate all the versions of the software that a bug is present in, rather than being limited to indicating a single version), and I imagine it results in reduced code overall for the app because of the use of metadata.
    1717
    1818== Object-Relational Mapper ==
    … …  
    3939(taken from [http://subissue.tigris.org/ Subissue], a project that aims to implement such a solution)
    4040
    41  * "Issues are stored directly in your Subversion repository, next to your source — right where they belong!" Ie. you have access to your Issues and project documentation (Wiki) by just checking out your source.
    42  * no extra RDBMS required - Subversion already has its own database
     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 * no extra RDBMS required; Subversion already has its own database.
    4343 * "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."
    4444