Context Navigation

Changes between Version 1 and Version 2 of Ticket #29787

v1	v2
1		I 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'.
	1	I ran into this bug when upgrading from 1.10 to 1.11. All my models have BigInteger ids. 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'.
2	2
3	3	After 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.