[Rpm-maint] [rpm-software-management/rpm] Sqlite improvements (#926)

[Panu Matilainen]

Okay, you track inode to detect rebuilds, that will cover the rebuilddb case but not the id wraparound one which ultimately needs to be handled anyway.

And yeah I know AUTOINCREMENT, but it comes with a cost.

BTW just realized that this change actually doesn't really change anything at all in the sqlite backend: it recycles the topmost ids as it is now, because it just does ""SELECT MAX(hnum)" + 1 instead of keeping a permanent record like the other backends do.

The real question is of course the wraparound and what to do about it - outsourcing to sqlite doesn't help a bit as it'll only wrap around at INT64_MAX which is 31 bits beyond our reach.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/926#issuecomment-550286251
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20191106/6acf1b3f/attachment.html>