mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
7a9e88eee6
If you had a foreign key set and then decided to add `on_delete: :cascade` later in another migration that migration would run but wouldn't refresh the schema dump. The reason for this was because `create_table_info` caches the statement and sets it to be the same as the original declaration for the foreign key (without the `on_delete: :cascade`. PR #25307 ended up fixing this bug because it removes the check for `create_table_info` and relies on reading from `information_schema`. The fix however was intended to patch another bug. The reason this fixes the issue is we're no longer parsing the regex from the cached `create_table_info`. This regression test is to ensure that the issue does not return if we for some reason go back to using `create_table_info` to set the foreign keys. |
||
|---|---|---|
| .. | ||
| change_schema_test.rb | ||
| change_table_test.rb | ||
| column_attributes_test.rb | ||
| column_positioning_test.rb | ||
| columns_test.rb | ||
| command_recorder_test.rb | ||
| compatibility_test.rb | ||
| create_join_table_test.rb | ||
| foreign_key_test.rb | ||
| helper.rb | ||
| index_test.rb | ||
| logger_test.rb | ||
| pending_migrations_test.rb | ||
| references_foreign_key_test.rb | ||
| references_index_test.rb | ||
| references_statements_test.rb | ||
| rename_table_test.rb | ||