#17713: allows_primary_key_0 is misnamed
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d3cf6cfacfb828faad4f4f97c904e259304649b3"]:
{{{
#!CommitTicketReference repository=""
revision="d3cf6cfacfb828faad4f4f97c904e259304649b3"
Fixed #17713 -- Renamed BaseDatabaseFeatures.allows_primary_key_0 to
allows_auto_pk_0.
MySQL does allow primary key with value 0. It only forbids autoincrement
primary key with value 0.
Thanks Claude Paroz for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17713#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.3cd74218cafe8361c14053f5ff1edc81%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
