Collision of multipart_id_numbering idnos after migration to new server.
After migrating the SQL database to another server (mysqldump + SQL-file import), and updating the code from v1.7.9 to v1.8 (git origin/develop), we suddenly had a serious number of colliding idnos, due to auto-increment of multipart_id_numbering handing out numbers that were already taken.
Reason yet unknown. Configuration was identical.
After spending hours to fix this mess, CA was still handing out wrong numbers, until I updated the "seq" value for that idno-signature in the table "ca_multipart_idno_sequences".
Seth wrote (in December 2019):
"The ca_multipart_idno_sequences table is still maintained but not actually used to generate next in sequence. It'll likely go away in the near future."
Do you have any idea what happened here?
Thanks in advance.