- marked as blocker
- changed title to Correct handling duplicate keys in the index.
Correct handling duplicate keys in the index
Issue #171
closed
Until #159 is implemented the records with duplicate keys should be allowed in the index, as it is now. However any changes applied to any of them apply to all of them, which is confusing and dangerous. For the time being a warning would be sufficient.
Comments (4)
-
reporter
-
repo owner
- marked as critical
-
assigned issue to
Michał Rudolf
- changed title to Correct handling duplicate keys in the index
-
repo owner
- changed status to open
-
repo owner
- changed status to closed
Rewrite handling of index entries. Closes
#145and#171. Now items are identified by their position in the file, not by the entry itself. Therefore homonyms are possible now. Entries are now fully editable, but for now the sort order won't be updated automatically if the word is edited and alphabetic/atergo order is used.Please look for regressions as plenty has changed.
→ <<cset dba42b4fa318>>
- Log in to comment
When working on the full data (https://bitbucket.org/jsbien/ilindecsv/src) I noticed a problem which didn't occur during my earlier tests: duplicate keys have different comments but share the same URL despite the fact that in the file the URLs are different, cf. e.g. kleszcz.
If this cannot be corrected quickly, then I have to redesign the index data :-(