Hacker News new | ask | show | jobs
by morgo 4023 days ago
This is caused by a layering problem in MySQL itself:

- Triggers are at the SQL Layer

- Foreign keys are implemented natively by InnoDB at the storage engine layer

It is not as easy to fix as it sounds.

1 comments

It's probably not, but I'd rather not have the feature at all than think that it's there and working but actually not doing what I've asked it to. The current short-term fix would be to make it raise an error when you try to create such a trigger, so at least no one would be using it for now.