#29787: ForeignKey to User with BigIntegerField id/pk gets created as 'integer'
instead of 'bigint' field in postgres
-------------------------------------+-------------------------------------
               Reporter:  Andrew     |          Owner:  nobody
  Badr                               |
                   Type:  Bug        |         Status:  new
              Component:  Database   |        Version:  1.11
  layer (models, ORM)                |
               Severity:  Normal     |       Keywords:
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 I ran into this bug when upgrading from 1.10 to 1.11. Doing a git bisect
 tracked it down to the 1.11.7->1.11.8 change, and specifically
 b8a2f3c2d66aa15af4be745a576609b958a853c0 is the first bad commit (fix for
 #28305).

 My test case creates a User model instance, then creates another model
 instance pointing to it via ForeignKey. On 1.11.7, this works fine, and
 inspecting the database shows the fk field as having type 'bigint' in
 postgres. On 1.11.8, the test fails, and inspecting the db shows the field
 as a regular 'integer'.

 I tried to repro with a minimal test case on a fresh project, but sadly
 was not able to recreate the bug. (It worked fine.) So there must be some
 other config in my project that's affecting this. If I have time I'll try
 to pin it down (already spent 2 hours on this), but maybe someone who
 worked on that patch can make an educated guess on what's happening?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29787>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.b4dfb0d64dd09b2c610ab81c600f4632%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to