Edgewall Software

Changes between Version 4 and Version 5 of MultipleRepositorySupport/Cache


Ignore:
Timestamp:
Apr 21, 2009, 10:41:15 AM (15 years ago)
Author:
Lele Gaifax <lele@…>
Comment:

Introducing TracDarcs/Cache

Legend:

Unmodified
Added
Removed
Modified
  • MultipleRepositorySupport/Cache

    v4 v5  
    127127=== Discussion ===
    128128
    129 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).
     129From 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.
    130130
    131 (short IRC transcription before going to bed, feel free to fix/clarify Lele ;-) )
     131There'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): [source:/sandbox/multirepos/trac/versioncontrol/admin.py@8070#L156 current implementation] does not scale very well, regardless of TracDarcs needs, though.
     132
     133I'm going to write some details in TracDarcs/Cache first, to keep the discussion clear.