#14286: Support for BigAutoField
-------------------------------------+-------------------------------------
Reporter: hongrich | Owner: mmcnickle
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by hhowe29):
Replying to [comment:23 dcramer]:
> In fact, I'd propose a new API be added to keys: "get_related_db_type"
(or something along these lines)
Yes please. Currently, ForeignKey.db_type is too tightly coupled to
AutoField and IntegerField. There should be a new method that ForeignKey
can call to ask the related field what SQL should be used to create a
foreign key to that type. BitAutoField would return 'bigint'. AutoField
would return a regular int. Most fields would simply defer to what db_type
already returns.
Someone has already submitted this: #13774
--
Ticket URL: <https://code.djangoproject.com/ticket/14286#comment:25>
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/066.b4d9001abad891570041b6c7c24a0f68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
