Why are we using "ON UPDATE SET NULL" in kohastructure.sql exactly? IMO it should be replaced with "ON UPDATE CASCADE", everywhere.
That does indeed seem strange to me... is it something around pseudoanonymisation perhaps? Generally, I think I'd expect to set 'ON UPDATE CASCADE ON DELETE SET NULL'
What are the cases where we would change ids though? These all seem to reference rows that are auto increment, or cannot be edited (itemtype) If you are changing one of these, is it the same object? Should the links between tables remain? I am fine either way, but I don't think it should be happening very often
(In reply to Jonathan Druart from comment #0) > Why are we using "ON UPDATE SET NULL" in kohastructure.sql exactly? IMO it > should be replaced with "ON UPDATE CASCADE", everywhere. Not so sure about that. You might loose much more than you want to.
(In reply to Marcel de Rooy from comment #3) > (In reply to Jonathan Druart from comment #0) > > Why are we using "ON UPDATE SET NULL" in kohastructure.sql exactly? IMO it > > should be replaced with "ON UPDATE CASCADE", everywhere. > > Not so sure about that. You might loose much more than you want to. Hmm. Thats DELETE for sure ;)