Changes between Version 2 and Version 3 of GenericTrac

Timestamp:

Feb 7, 2007, 9:43:04 AM (17 years ago)

Author:

Christian Boos

Comment:

Note about #130

GenericTrac

@@ -4 +4 @@
  - TracDev/Proposals/DataModel
  - TracDev/Proposals/Journaling
+ - WikiContext are used as ''resource descriptors'' and have a `.resource` field 
+   which enables one to fetch the corresponding data model instance
 
 See also [googlegroups:trac-dev:8cf3f5fe0e476ce5 this mail].
 
+== Design Notes ==
+
+As this will be a major redesign of the data model, it will also be a good opportunity to tackle the ''[TracMultipleProjects multiple project support]'' in Trac (#130).
+
+Each resource related table should probably get a `project` identifier field.
 
 == Current Status ==
@@ -34 +41 @@
 -- 
 create table milestone_prop (
+ project text,
  id    text,
+ --
  name  text,
  value text
@@ -43 +52 @@
 -- record Milestone change metadata
 --
-create table milestone_rev (
+create table milestone_revision (
  tid            int primary key,
+ --
  date           int,
  authname       text,
@@ -52 +62 @@
 );
 
-create index milestone_date_idx on milestone_journal ( date );
-create index milestone_authname_idx on milestone_journal ( authname, authenticated );
+create index milestone_date_idx on milestone_revision ( date );
+create index milestone_authname_idx on milestone_revision ( authname, authenticated );
 
 -- Track changes of Milestone properties
 --
-create table milestone_history (
+create table milestone_change (
  tid   int,
+ project text,
  id    text,
+ --
  name  text,
  value text,
- unique (tid, id)
+ unique (tid, project, id)
 );
 
@@ -68 +80 @@
 --
 create table milestone_schema (
- name     text primary key,
+ project  text,
+ name     text,
+ --
+ revprop  char,
  type     text,
  detail   text,
  value    text,
  order    int,
- revprop  char
+ unique (project, name)
 );
 }}}
@@ -79 +94 @@
 The existing `milestone` table can be kept, it will simply not be used anymore.
 This will allow to test the branch within existing environments.
+
+The `name` is not unique in `milestone_change`, to allow multiple values (#918)