Context Navigation

MultipleProject

-              v14
+              v15
 An additional `project` table is also needed, and it can take the form of a ''resource table specialization'' described in GenericTrac. Projects should have at least a ''description'' field, a ''creator'' and a ''status'' field. Projects can be linked explicitly to shared data. For example, each projects can be linked to its own set of repositories.
+||||||||||||||||||= Project ||
+||= field     || uid || id || Parent || summary || description || Creator || created || status ||
+||= DB type   || int || text || int || text || text || int || int64 || text ||
+||= subtype   || key || plain || references Project || wiki || wiki || references User || usecs || plain? ||
 For SQL queries that may cover more than one project, a helper method can be used to form the include/exclude constraints, given the project pattern list that has to be used.
 On the API side, the multi-project nature will be mostly transparent except when instantiating and manipulating resources, which will have an additional `project` field. Legacy resources and legacy code not taking the project into account will simply fallback to accessing resources at the global level.
+On the API side, the multi-project nature will be mostly transparent except when instantiating and manipulating resources. Legacy resources and legacy code not taking the project into account will simply fallback to accessing resources at the global level.