#33709: Primary key of m2m tables is not migrated to BigAutoField
-----------------------------------------+------------------------
               Reporter:  Jeremy Lainé   |          Owner:  nobody
                   Type:  Uncategorized  |         Status:  new
              Component:  Uncategorized  |        Version:  3.2
               Severity:  Normal         |       Keywords:
           Triage Stage:  Unreviewed     |      Has patch:  0
    Needs documentation:  0              |    Needs tests:  0
Patch needs improvement:  0              |  Easy pickings:  0
                  UI/UX:  0              |
-----------------------------------------+------------------------
 I am trying to upgrade an existing application's models to use only
 "bigint" primary keys on postgresql. To do this I changed
 DEFAULT_AUTO_FIELD to BigAutoField, generated the migrations then applied
 them.

 The tables for my explicitly defined models get upgraded correctly. The
 many-to-many intermediate tables on the other hand still have an "integer"
 primary key, with the 32bit limit I'm trying to avoid.

 The following model are sufficient to reproduce the issue:

 ```
 class Book(models.Model):
     name = models.CharField(max_length=255)
     tags = models.ManyToManyField("Tag")


 class Tag(models.Model):
     name = models.CharField(max_length=255)
 ```

 The resulting schema for the testapp_book_tags looks like:

 ```
 test=> \d testapp_book_tags;
                              Table "public.testapp_book_tags"
  Column  |  Type   | Collation | Nullable |                    Default
 
---------+---------+-----------+----------+-----------------------------------------------
  id      | integer |           | not null |
 nextval('testapp_book_tags_id_seq'::regclass)
  book_id | bigint  |           | not null |
  tag_id  | bigint  |           | not null |
 ```

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33709>
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/01070180c36a402d-99c0d6dc-4526-45d8-9597-3f1f4cbba554-000000%40eu-central-1.amazonses.com.

Reply via email to