MySQL may or may not quietly ignore transactions and foreign keys and invalid values (substituting incorrect values that happen to be valid), depending on how i

MySQL may or may not quietly ignore transactions and foreign keys and invalid values (substituting incorrect values that happen to be valid), depending on how it's configured, and the defaults are mostly wrong (unsafe). And as far as I know there is still no option for "make my transaction fail if I try to use a table that doesn't support transactions".