migrations
migrations copied to clipboard
Foregin_check=0 changes the sql result.
We set foreign_key_checks = 0 and that's have some consequences.
Running migrations with ON DELETE RESTRICT produces table with ON DELETE NO ACTION. In MySQL they are identical, still, I see this as a bug.
Also, disabled foreign_key_check may lead to hard-to-catch errors and we should not enable it by default. A migration can enable it by itself. So, I suggest removing it.
unfortunately removing it would be a BC break, maybe wait for 4.0?