|Version 2 (modified by 15 years ago) ( diff ),|
Currently, Trac uses SQLite as its database backend.
However, there has been several requests that other databases should be supported as well (see #126).
There has been an attempt to provide support for PostgreSQL: source:/branches/rocky-dev/features/postgresql_support/ though this branch is not so active this days…
I think some people have been talking about using SQLObject to accomplish this goal of database independence.
Data Model Changes
If SQLObject works well, this proposal may not be necessary, but I would like some feedback (brad at dsource dot org) on the following proposal: TracTicketDataModelChanges
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.