Edgewall Software

Changes between Initial Version and Version 1 of Ticket #11727


Ignore:
Timestamp:
Aug 21, 2014, 3:47:36 PM (10 years ago)
Author:
Jun Omae
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11727

    • Property Keywords svn cache added; mysql resync removed
    • Property Component database backend → version control
    • Property Milestone 1.0.2 → next-stable-1.0.x

  • Ticket #11727 – Description

    initial v1  
    11We've faced the following problem: when there's a simultanious addition of the file and replacement of the same file in one ticket, trac is unable to synchronize such a commit and the whole process stops. The cause of the error lies here: the 'Replacing' type of change is put to database as adding a new file and as a result we get the duplicate of the database. Here's the dump of sql quieries trac has sent to database:
    2 
    3      58 Query INSERT INTO node_change
    4                     (repos,rev,path,node_type,change_type,base_path,
    5                      base_rev)
    6                 VALUES (1,'0000011999','branch/debug_GC/tools/src/gameserver/MyTools/DropListGenerator.java','F','A',NULL,-1)
    7      58 Query INSERT INTO node_change
    8                     (repos,rev,path,node_type,change_type,base_path,
    9                      base_rev)
    10                 VALUES (1,'0000011999','branch/debug_GC/tools/src/gameserver/MyTools/DroplistGenerator.java','F','A',NULL,-1)
    11 
     2{{{
     358 Query INSERT INTO node_change
     4               (repos,rev,path,node_type,change_type,base_path,
     5                base_rev)
     6           VALUES (1,'0000011999','branch/debug_GC/tools/src/gameserver/MyTools/DropListGenerator.java','F','A',NULL,-1)
     758 Query INSERT INTO node_change
     8               (repos,rev,path,node_type,change_type,base_path,
     9                base_rev)
     10           VALUES (1,'0000011999','branch/debug_GC/tools/src/gameserver/MyTools/DroplistGenerator.java','F','A',NULL,-1)
     11}}}
    1212Synchronization of the data stops after that and all the changes following this problem revision are not seen by trac