The question is if one should "fix" this at all. If you change the behavior from "foreign keys do not activate triggers" to "foreign keys activate triggers", everyone who uses triggers will have to audit their applications for potential problems. And for large applications, that can be a lot of work.
MariaDB documents "foreign keys do not activate triggers" as the standard behavior:
Personally, I am grateful for software that changes as seldom as possible. I don't want to spend time on "updating" my application because something down in the stack changed.
Comments
The question is if one should "fix" this at all. If you change the behavior from "foreign keys do not activate triggers" to "foreign keys activate triggers", everyone who uses triggers will have to audit their applications for potential problems. And for large applications, that can be a lot of work.
MariaDB documents "foreign keys do not activate triggers" as the standard behavior:
https://mariadb.com/kb/en/mariadb/trigger-limitations/
Personally, I am grateful for software that changes as seldom as possible. I don't want to spend time on "updating" my application because something down in the stack changed.
Well what does SQL standard say about that?
Application can just not update, so there is no need for windows level of compatibility management
Personally never jumped on the mysql train and can say I'm really glad for that.