#25012: Migrations don't make foreign key type changes
-------------------------------------+------------------------------------
     Reporter:  Hedde van der Heide  |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Migrations           |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  migrations           |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+------------------------------------

Comment (by Rowan Seymour):

 Having experimented a bit more - it seems changing a primary key to
 `BigAutoField` does change any foreign keys to `BIGINT` when the migration
 is applied - ''except'' in implicit M2M through models. Those remain as
 `INT` and have to be fixed manually.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/25012#comment:14>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.de3d3db17f4070495e10ebcf67ff6cbf%40djangoproject.com.

Reply via email to