#26730: Make AutoField consistent between postgresql and mysql
-------------------------------------+-------------------------------------
Reporter: hellerve | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: duplicate
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 MarkusH):
FTR, I took a look at #56 during the PyCon sprints. The only sensible way
to implement it is IMO a `PositiveAutoField`.
The primary key column on PostgreSQL is an `integer` (-2147483648 to
+2147483647) and the related sequence a `bigint` (-9223372036854775808 to
+9223372036854775807) with min_value=1, max_value=9223372036854775807.
https://www.postgresql.org/docs/9.5/static/datatype-numeric.html
SQLite doesn't allow unsigned integers for PK columns.
MySQL supports `integer UNSIGNED` for PK, but that's not backwards
compatible to the existing code base.
--
Ticket URL: <https://code.djangoproject.com/ticket/26730#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f5c816e274743859964754ef84a3eaf8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
