#36064: save() behavior for new model instance with default primary key does not
apply to CompositePrimaryKey
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Csirmaz
| Bendegúz
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"8287fd49151b1b99045efbf3de8ef911d63c5f45" 8287fd49]:
{{{#!CommitTicketReference repository=""
revision="8287fd49151b1b99045efbf3de8ef911d63c5f45"
Refs #36064 -- Added test that falsey primary key default/db_default value
skips an update query on save.
This adds test coverage for logic change in
9fa4d07ce0729850661a31a6b37c6b48f13d2266.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36064#comment:11>
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 visit
https://groups.google.com/d/msgid/django-updates/010701944fd00d6a-f9ba59b4-e124-48e2-981f-9841b67440cd-000000%40eu-central-1.amazonses.com.
