#19463: Add UUID Field to core
-------------------------------------+-------------------------------------
Reporter: guettli | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by loic84):
* cc: loic@… (added)
Comment:
Big +1 on @akaariai's GeneratedField idea.
For example I use extensively what I call a "readable unique ID", similar
to YouTube video IDs (i.e. "sc5vraPpTcA") for which I made a custom Field.
It functions like a UUID but trades the creation convenience (guaranteed
uniqueness) for usage convenience (being able to read it out load, shorter
URL, etc.). A GeneratedField would allow me to implement that cleanly.
That said, some databases have native support for UUIDs and it's pretty
much the standard for sharding, so we could have the generic
GeneratedField and a UUIDField subclass.
I'd work on a patch with some guidance from @akaariai.
--
Ticket URL: <https://code.djangoproject.com/ticket/19463#comment:12>
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/065.db63725063fb036e11c95a746c69b353%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
