https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #36 from Kai Krakow <k...@kaishome.de> --- Oh, nice... Sometimes it helps to talk about a few things. I could think of the following solution: Add another UUID->CounterID mapping table to the database, that is easy to achieve. Everytime we encounter a new UUID, we increase the CounterID one above the maximum value in the DB and use that as a file system identifier. We can now bit-reverse the CounterID so that the least-significant bits switch position with the highest. The result will be XOR'ed with the 64-bit inode number. Et voila: There's a DocID. What do you think? -- You are receiving this mail because: You are watching all bug changes.
