#29787: ForeignKey to User with BigIntegerField id/pk gets created as 'integer'
instead of 'bigint' field in postgres
-------------------------------------+-------------------------------------
Reporter: Andrew Badr | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Badr):
Indeed, it looks like resetting my migrations (à la
https://simpleisbetterthancomplex.com/tutorial/2016/07/26/how-to-reset-
migrations.html) fixed the problem, so this has something to do with the
migrations code. Maybe the data type for foreign keys is being determined
too early in certain cases somehow?
--
Ticket URL: <https://code.djangoproject.com/ticket/29787#comment:3>
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/068.b0feeb0e84a02cf3ad9cd37c3ba90f9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
