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 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.