You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2024. It is now read-only.
The method to get the next rev_id doesn't always match the next value that will be inserted in the revision table. The revision table uses a sequence to insert the next row. In the case where a record was deleted, max +1 would not equal the next sequence # of the rev_id. It's probably not an issue on a fresh system or one where no deletes have been performed.
The text was updated successfully, but these errors were encountered:
The method to get the next rev_id doesn't always match the next value that will be inserted in the revision table. The revision table uses a sequence to insert the next row. In the case where a record was deleted, max +1 would not equal the next sequence # of the rev_id. It's probably not an issue on a fresh system or one where no deletes have been performed.
The text was updated successfully, but these errors were encountered: