Hi Michael, not sure then :( Maybe someone else has an idea? Katrin On 25.08.22 18:39, Michael Kuhn wrote:
Hi Katrin
You wrote:
the fix did prevent the problem from occurring on older versions, but it doesn't fix the data.
Could it be the bad data was there before, maybe from using an older DBMS version?
The simplest fix is to delete the entries in the old_ and deleted_ tables with the doubled up IDs and then restart your DBMS.
Yes, I know the fix won't fix the data. So I usually do what you suggested.
But I had expected the fix to prevent the problem from occurring - only the "auto_increment fix" does NOT prevent the problem in MariaDB 10.5.51. Instead from time to time new deletions (not all) produce the same error again.
That's why I wrote I'm not sure if the underlying problem is the same as the one that was fixed by the "auto_increment fix".
Best wishes: Michael