Changes between Version 32 and Version 33 of GenericTrac

Timestamp:

Aug 3, 2010, 6:44:22 PM (14 years ago)

Author:

Christian Boos

Comment:

a few more details on the sequence number

GenericTrac

@@ -17 +17 @@
 == Related Proposals ==
 
-This stems from the following former proposals:
- - TracObjectModelProposal
- - TracDev/Proposals/DataModel
- - TracDev/Proposals/Journaling
-
-See also [googlegroups:trac-dev:8cf3f5fe0e476ce5 this mail].
+The idea is not new, it has its root in the TracObjectModelProposal, and was refined several times (TracDev/Proposals/DataModel, TracDev/Proposals/Journaling, see also [googlegroups:trac-dev:8cf3f5fe0e476ce5 this mail).
 
 As this will be a major redesign of the data model, 
@@ -98 +93 @@
  ||= id ||= prop ||= value ||= seq ||
 
-//seq// is the sequence number in case of multiple entries with the same property name.
+//seq// is the sequence number, which is used to support multiple values for the same property.
 
 Note by the way that newer "resources", like `repository` in MultiRepos already have this `(id,prop,value)` form, we'd only have to add `seq`.
+
+Note also that this sequence number could be a globally unique sequence number, which would make it possible to use it as a foreign key in specialized tables, in case properties are needed to describe the resource - property relation itself...
 
 ==== Schema