Changes between Version 52 and Version 53 of TracMultipleProjects/ComprehensiveSolution

Timestamp:

Apr 13, 2008, 2:15:48 PM (16 years ago)

Author:

karl.debisschop@…

Comment:

add author to previous comment

TracMultipleProjects/ComprehensiveSolution

@@ -144 +144 @@
    - Is there a possibility to reach the same thing with sqlight?
    - ''Not in this way; this particular scheme relies on the unique ability of PostGreSQL to use multiple schemas in the same database and do queries across those schemas.  If you don't care about cross-project queries, then of course SQLite should work fine.'' [[br]] -- dave 01/28/2008
-   - The migration and multitrac query use schema but do not actually use the inheritance feature in postgresql, so its not clear to me how this is actually much more than a union query where the joined queries are set in a loop. If you use inheritance, you could simplify the multitrac_query to be a join like "select bar, relname from foo join pg_class on pg_class.oid=foo.tableoid;" This does not alter the trac schema at all, so I think trac DDL changes with version upgrades should work. I've modifiyed sqlite2pq and migrate.py to use inheritance. Any interest in persuing this variation on your approach?
+   - The migration and multitrac query use schema but do not actually use the inheritance feature in postgresql, so its not clear to me how this is actually much more than a union query where the joined queries are set in a loop. If you use inheritance, you could simplify the multitrac_query to be a join like "select bar, relname from foo join pg_class on pg_class.oid=foo.tableoid;" This does not alter the trac schema at all, so I think trac DDL changes with version upgrades should work. I've modifiyed sqlite2pq and migrate.py to use inheritance. Any interest in persuing this variation on your approach? [[br]] -- karl 04/13/2008
 
 ----