There's now a workaround for this. Instead of adding a new dbiSetNextInstance
call I've opted to change the put functions to make sure that the next instance
counter will be higher than the stored package.
For ndb this change is trivial. The sqlite backend doesn't need changing.
For lmdb/db3
@mlschroe pushed 1 commit.
de1a21071913b20bbb98a2aadf7991ae8e048304 Implement automatic conversion of the
database
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
That's also incorrect. It doesn't copy the "next package" counter, so adding
new packages will overwrite old ones.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
