https://bugs.kde.org/show_bug.cgi?id=436738
--- Comment #9 from pbs3...@googlemail.com --- > Now we are talking a bit more general. Should we split this into two bug > reports? If you're considering enlarging the scope of the bug report, then this may provide an opportunity to fix both this issue and the file-rename issue all at once. How about storing a docdata file whose name is the hash of the file size and the first 4kB (or middle 4kB, or whatever). Assume this is as good as a hash of the whole file, though obviously less expensive to compute. Store in the docdata file all full filepaths where this document has been opened from. (This is already done, according to Comment 7.) Purge from each docdata file any filepaths that have been deleted, and purge any docdata files that have had no filepaths for 6 months (or some configurable expiration period). Do this in an amortised / randomised fashion, only checking a few files on each startup, to keep the io negligible. That fixes file rename. To deal with modifications, create soft links "full path" -> "docdata file" in docdata directory. If a file is opened with no matching docdata file for its hash, search instead by filename, and if one is found, use that. (And write out a new docdata file named by the hash.) Purge old links where the path no longer exists in an amortised manner similar to before. Has something like this been previously considered and ruled out? -- You are receiving this mail because: You are watching all bug changes.
