diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-12-13 10:40:50 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-12-13 10:46:24 -0400 |
| commit | b159fc00324d6fd0e664b21a8b609ec48f8c7b2d (patch) | |
| tree | b4335b3c7dc2be745f5d8450dab72f5d0724af72 /doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment | |
| parent | e3fa232df35d360aa4e0343af4cdb0d223bb4bb5 (diff) | |
analysis
Diffstat (limited to 'doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment')
| -rw-r--r-- | doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment | 16 |
1 files changed, 16 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 new file mode 100644 index 000000000..8f8447491 --- /dev/null +++ b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-12-13T14:40:02Z" + content=""" +I thought this would involve the journal, but it seems not; same +behavior occurs if the journal is committed after each metadata change. + +Looking at the new metadata value in the case where a and c both get set, +it is: + + MetaData (fromList [(MetaField "f",fromList [MetaValue (CurrentlySet True) "a",MetaValue (CurrentlySet False) "c"])]) + +That is supposed to unset c, with the CurrentlySet False, but instead c +remains set somehow. +"""]] |