After you manually insert anything in a auto inc pk column you boobytrapped your table waiting for auto pk insertions to collide nastily. Lots of users have had to roll their own collision prevention or even create their own PK tables. As if you ever have pk autoinc columns and manual data migration you will run into this problem.

Auto Inc PKs should skip the value and attempt the next one or start at the max value or smth. GL!

Requested by @Pepn via the SpacetimeDB site.