Changes between Initial Version and Version 2 of Ticket #28065
- Timestamp:
- Apr 10, 2017, 5:32:17 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28065
- Property Cc added
-
Ticket #28065 – Description
initial v2 1 If you just add a {{{related_name}}} to an existing foreign key, it will require a migration which then drops and re-creates the foreign key. This is a non-DB, {{{meta}}} change only and shouldn't create a migration. 1 If you just add a {{{related_name}}} to an existing foreign key, it will require a migration which then drops and re-creates the foreign key. This is a non-DB, {{{meta}}} change only and shouldn't create a migration. This is with MySQL. 2 2 3 3 With Models: … … 47 47 ] 48 48 }}} 49 The {{{CREATE_INDEX}}} for both migrations is identical:49 The {{{CREATE_INDEX}}} result in {{{sqlmigrate}}} for both migrations is identical: 50 50 {{{ 51 51 CREATE INDEX "polls_jobdetail_job_id_5561ba44" ON "polls_jobdetail" ("job_id");