#32577: Add support for `UUIDAutoField` `DEFAULT_AUTO_FIELD`
-------------------------------------+-------------------------------------
Reporter: Tomasz Wójcik | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tomasz Wójcik):
Replying to [comment:6 Ian Foote]:
> > I don't think this field has to be very generic because DBs pk types
are very limited. As far as I know, only ints and UUIDs make sense for pk.
>
> While I'm not sure it would make sense in an {{{AutoField}}}, string
primary keys are possible. For example, you could use a language code
({{{en}}}, {{{fr}}}, {{{de}}}, etc) as a primary key.
Sure, my phrasing wasn't the best. What I meant is I think users only use
numeric types and uuids for generic app-wide primary keys so I don't think
it's necessary to allow other types for {{{AutoField}}}, such as string.
So instead of refactoring the entire {{{AutoField}}}, another type -
{{{UUIDAutoField}}} could be added.
--
Ticket URL: <https://code.djangoproject.com/ticket/32577#comment:7>
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.2c32670dbc4cfb563694b3c3ed90f1e4%40djangoproject.com.
