Re: Any plans to fix trigger bug relating to cascading foreign keys?

[Peter Brawley]

That isn't the only InnoDB ACID compliance issue ...

1. InnoDB allows non-unique foreign keys. If the parent key has duplicates, InnoDB permits deletion of none of them if there is a matching child row.

2. Some errors do not rollback the entire transaction they occur in. To fix that you have to use a HANDLER.

3. Self-referential ON UPDATE CASCADE and ON UPDATE SET NULL are not supported; recursion on them acts like RESTRICT. CASCADE may be nested only to 15 levels.

4. Checks on UNIQUE and FOREIGN KEY constraints cannot be deferred until the end of a statement; they are checked row by row, so it is impossible to delete a row which refers to itself via a foreign key.

Not sure what the fix priorities ought to be.

PB