Changes between Version 3 and Version 4 of MultipleRepositorySupport/Cache

Timestamp:

Apr 20, 2009, 10:36:38 PM (15 years ago)

Author:

Christian Boos

Comment:

integer identifiers for the repository?

MultipleRepositorySupport/Cache

@@ -96 +96 @@
  - This ''might'' work for 1) if we simply use NULL for the repos, as by the magic of using SHA1 keys, both Mercurial and Git have changeset ids that are globally unique 
 
+
+== Current Design ==
+
+(taken from source:sandbox/multirepos/trac/db_default.py@8081)
+{{{
+#!python
+    # Version control cache
+    Table('repository', key=('id', 'name'))[
+        Column('id'),
+        Column('name'),
+        Column('value')],
+    Table('revision', key=('repos', 'rev'))[
+        Column('repos'),
+        Column('rev'),
+        Column('time', type='int'),
+        Column('author'),
+        Column('message'),
+        Index(['repos', 'time'])],
+    Table('node_change', key=('repos', 'rev', 'path', 'change_type'))[
+        Column('repos'),
+        Column('rev'),
+        Column('path'),
+        Column('node_type', size=1),
+        Column('change_type', size=1),
+        Column('base_path'),
+        Column('base_rev'),
+        Index(['repos', 'rev'])],
+}}}
+
+=== Discussion ===
+
+From IRC, lelit (author of the TracDarcs plugin) suggested that using a ''surrogate id primary key'' for the repository would be more adequate for his use case, as he's re-using the `CachedRepository` and extending it with extra information, that extra information being stored in additional tables (e.g. for binding an artificial integer revision id to the corresponding Darcs hash and Darcs name): when renaming a repository, he would have to update his tables as well. There's currently no extension point for reacting to such changes, but the idea was that if we were using an unique integer id for the repository, there would be no need to update anything after a simple renaming (i.e. the repository name would be just another repository property).
+
+(short IRC transcription before going to bed, feel free to fix/clarify Lele ;-) )