Actions
Feature #13277
open
Don't store changesets for DVCS on databases
Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
I believe that this is a major mistake, to load on the database changesets from DVCS. I can see that there may be a reason to store then if you are dealing with CVS/SVN but not with GIT, Bazaar and Mercurial.
This ends-up bloating the database with something that you can query locally. There is no reason not to use local data for that.
This also enables working with big repositories, that otherwhise would probably crash redmine during the "import phase" repositories went on before showing the latest revisions.
Updated by Ebrahim Mohammadi over 10 years ago
Well, makes sense.
Is it possible to implement search directly on the code repository without loading the revision comments in database?
Actions