diff options
| -rw-r--r-- | doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment index 9541f1d74..4f82db153 100644 --- a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment +++ b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment @@ -19,4 +19,6 @@ timestamp, and indeed the same timestamp is used for all the batch changes. With the same timestamp for the log line that sets c as the line that removes it, it's indeterminite which line will be acted on first, and so the removal can be processed before the addition, leaving c "stuck". + +Fixing.. """]] |