In the process of adding support for MySQL, a workaround for a MySQL bug was added in commit b4de56a64e. According to one source, however, the correct fix is to formulate the foreign key constraint as a table (rather than column) constraint, which makes the foreign key actually work.
As this will require a schema change, it should be batched with other schema changes.
In the process of adding support for MySQL, a workaround for a MySQL bug was added in commit b4de56a64ea4c0a98b9f7ac371b0b4de82eb9910. According to [one source](https://grimoire.ca/mysql/choose-something-else#validity), however, the correct fix is to formulate the foreign key constraint as a table (rather than column) constraint, which makes the foreign key actually work.
As this will require a schema change, it should be batched with other schema changes.
jking
added this to the Future milestone 5 years ago
In the process of adding support for MySQL, a workaround for a MySQL bug was added in commit
b4de56a64e. According to one source, however, the correct fix is to formulate the foreign key constraint as a table (rather than column) constraint, which makes the foreign key actually work.As this will require a schema change, it should be batched with other schema changes.