Changes between Version 2 and Version 3 of TracMultipleProjects/MultipleEnvironmentsSingleDatabase

Timestamp:

Apr 18, 2006, 11:54:08 PM (18 years ago)

Author:

greg@…

Comment:

possible alternative to views

TracMultipleProjects/MultipleEnvironmentsSingleDatabase

@@ -45 +45 @@
  * Since multiple projects are using the same ticket id sequences, there will be gaps in the ticket numbers for each project. I don't think this is a big deal, but I thought I'd mention it.
  * I don't know how this affects version control features, since I have those turned off right now.
+
+== Possible Alternative ==
+
+Using this as inspiration I also create a different user for each trac project in the postgres database but I then create a schema for each user. Any tables in the database which need to be different for each project stay in the user schema while all the common ones (tickets, etc) stay in the public schema. This has the advantage that initenv and possibly upgrade all work with the caveat that you may need to go in and remove tables from the user schema that get created. I have this mostly working on a standard Centis 4.3 system using trac /trunk (0.1dev). I can now select which parts of trac are per project and which are global.