Switch to using the same DB4 instance as Subversion

[anonymous]

It would be very nice if Trac ran on the same database instance as Subversion. [I do not know much about db4 - if it supports namespaces, that would be great. Otherwise you can just prefix all tables with 'trac_'…)

This would have obvious management advantages - instead of having to maintain two different DB systems (db4 and PySQL) and develop dual set of backup/recovery procedures, there would be only one DB to maintain. [And since Trac is intimately tied to Subversion, it is safe to assume that DB4 is already installed on the machine running Trac]

[anonymous]

This was addressed on the mailing list. Quoting:

• SQLlite is … lite and very fast. You cannot get that speed with a BDB database. Do no forget Trac Wiki pages are generated on-the-fly.
• BDB does not support SQL interface. Which means another layer should be added to translate SQL statement into BDB requests
• SQLlite provides all the features Trac needs. BDB would be an overkiller for this kind of application
• It is not true anymore that Subversion uses BDB: it can use BDB, but it also can use its proprietary repository backend (FSFS, starting release 1.1). Trac should not add a dependency onto BDB if one uses Subversion FSFS backend