#56: Primary key columns should be UNSIGNED
-------------------------------------+-------------------------------------
Reporter: Manuzhai <mail@…> | Owner: Caio
| Ariede
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: mysql | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* needs_better_patch: 1 => 0
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
I don't think it's necessary anymore to change the default behavior. We
have `PositiveBigIntegerField` in Django 3.1 (#30987) and a way to change
the default `AutoField` in Django 3.2+ (#31007). As a workaround folks can
use `DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'` or an explicit
primary key `id = models.PositiveBigIntegerField(primary_key=True)`, see
[https://groups.google.com/g/django-developers/c/VFXZpHnuEJc the mailing
list discussion].
--
Ticket URL: <https://code.djangoproject.com/ticket/56#comment:50>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/085.209d151f5ff6882954fcf7c7b3f3cc07%40djangoproject.com.
