Changes between Version 3 and Version 4 of Ticket #29574, comment 9


Ignore:
Timestamp:
Nov 11, 2022, 11:18:50 AM (2 years ago)
Author:
Bhuvnesh

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29574, comment 9

    v3 v4  
    332. Now when we run second migration, table A is created and B is recreated with field {{{a_ptr}}} as primary key and all the old fields  of B are deleted(even{{{id}}}). No changes for table C.
    443. Since {{{c.fk}}} still points to {{{b.id}}} (at physical level), it throws {{{foreign_key_mismatch}}} error.
    5 4. If we explicity define primary key in model B everything works as expected.
     54. If we explicity define primary key in model B everything works as expected.(temporary solution)
    66{{{
    77bid = models.IntegerField(primary_key=True)
Back to Top