#31785: Documentation suggesting using UUIDField as a good alternative for
primary_key, without inviting to consider performance drawbacks
-------------------------------------+-------------------------------------
Reporter: Remy | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.0
Severity: Normal | Resolution: invalid
Keywords: uuid uuidfield | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
> What is the take of the community regarding that?
The DevelopersMailingList is the appropriate venue for this kind of
question/discussion.
There was some discussion of this here: https://groups.google.com/d/topic
/django-developers/VFXZpHnuEJc/discussion which led to #31007.
I cannot recall exactly what the consensus opinion on using UUID PKs was.
(I've certainly done it in the past without experiencing particular issues
but...)
Will close as invalid for now, since the mailing list is the place for it,
but happy to re-open/accept if there's a consensus reached.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/31785#comment:1>
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/067.dac3fe2e51beb297c4585c1c0b51ccf9%40djangoproject.com.
