#31785: Documentation suggesting using UUIDField as a good alternative for
primary_key, without inviting to consider performance drawbacks
-------------------------------------+-------------------------------------
Reporter: Remy | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: 3.0
Documentation |
Severity: Normal | Keywords: uuid uuidfield
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In the documentation section regarding UUIDFields
([https://docs.djangoproject.com/en/3.0/ref/models/fields/#uuidfield]), we
have:
{{{
Universally unique identifiers are a good alternative to AutoField for
primary_key
}}}
However the question of whether UUIDs make good primary keys regarding to
performance appears to be debated: https://www.percona.com/blog/2019/11/22
/uuids-are-popular-but-bad-for-performance-lets-discuss/
What is the take of the community regarding that?
In any case if there is doubt, having mention of that in the documentation
should be considered.
--
Ticket URL: <https://code.djangoproject.com/ticket/31785>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.ed8d60c87fa2832afde3d5a6c91438c2%40djangoproject.com.
