Re: M:N-like table with a contents, updating the PK leads to problems

markus, thanks! > On 11. 10. 2022, at 11:55, mailinglists wrote: > Thou shall never ever change a primary key! Yup, I suspected that it would be the culprit. > Replace the compound PK with a “real” ID and be done. This is not such a big > thing to do. I've done this several times. You need a

Re: M:N-like table with a contents, updating the PK leads to problems

Thou shall never ever change a primary key! Replace the compound PK with a “real” ID and be done. This is not such a big thing to do. I've done this several times. You need a bit of SQL to “fix” your database, but that is no rocket science. This m:n join table is not a mere technical