#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):
I understand it's out of scope for 3.2 as you already have a RC though I
think docs could mention it has to subclass `AutoField`.
{{{
The type of this implicit primary key can now be controlled via the
DEFAULT_AUTO_FIELD setting and AppConfig.default_auto_field attribute. No
more needing to override primary keys in all models.
}}}
This could be more specific as it doesn't apply to UUID pk projects.
----
I'm glad it's accepted as a feature request, thanks. I'm looking forward
to hearing how you want this to be tackled. And as I said, I'm happy to
open a PR as I want to use it with UUIDs in my next project.
--
Ticket URL: <https://code.djangoproject.com/ticket/32577#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.0bdf93eee303dc96668ff3c70affecdc%40djangoproject.com.
