Changes between Initial Version and Version 1 of Ticket #29787


Ignore:
Timestamp:
Sep 23, 2018, 7:44:53 PM (6 years ago)
Author:
Andrew Badr
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29787 – Description

    initial v1  
    1 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).
     1I ran into this bug when upgrading from 1.10 to 1.11. My test case creates a User model instance, then creates another model instance pointing to it via ForeignKey. On 1.10, this works fine, and inspecting the database shows the fk field as having type 'bigint' in postgres. On 1.11, the test fails, and inspecting the db shows the field as a regular 'integer'.
    22
    3 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'.
     3After some digging, I've found that this bug happens, oddly, at different commits for different models. For some models (??) it occurs starting in 45ded053b1f4320284aa5dac63052f6d1baefea9 (#27666). For others, b8a2f3c2d66aa15af4be745a576609b958a853c0 is the first bad commit (fix for #28305; comes between 1.11.7 and 1.11.8). The fact that the former has to do with migrations might be a clue.
    44
    5 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?
     5I 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 ~4 hours on this), but maybe someone who worked on the relevant patches can make an educated guess on what's happening?
Back to Top