David Abrahams wrote:
And if I have existing Tracs in databases, can I move them into PostgreSQL schemas?
Depends on how good your SQL-foo is. If they are already in PostgreSQL, it's fairly trivial. I'd probably suggest doing a pg_dump into a plain text format. Then you can edit the dump file and add something like the following (untested):
create schema bob; set search_path to bob; at the top, and that should do it.
It looks really attractive. There are only two apparent problems: 1. Migrating existing multiple Tracs into a single one doesn't sound trivial.
No, it doesn't
2. it seems like it would be hard to control Wiki access nicely. I don't really want to manually exert control on a page-by-page basis; in fact, what I get now with separate Tracs is almost ideal where the Wikis are concerned: there's a big playground for each client where they can create and view pages at whim. I suppose one might fake it by allowing a client to create/view pages with a particular prefix or something...
Using a particular prefix is probably the best (only?) way to handle permissions for multiple projects
-John _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
