Edgewall Software

Changes between Version 14 and Version 15 of TracDev/Proposals/MultipleProject


Ignore:
Timestamp:
Nov 28, 2014, 12:57:30 AM (5 years ago)
Author:
Christian Boos
Comment:

add the Project table

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/MultipleProject

    v14 v15  
    139139An 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.
    140140
     141||||||||||||||||||= Project ||
     142||= field     || uid || id || Parent || summary || description || Creator || created || status ||
     143||= DB type   || int || text || int || text || text || int || int64 || text ||
     144||= subtype   || key || plain || references Project || wiki || wiki || references User || usecs || plain? ||
     145
     146
    141147For 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.
    142148
    143 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.
     149On 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.
    144150
    145151