#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: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
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
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"585160586336f3bcd7b694f53cf10db73c56981c" 5851605]:
{{{#!CommitTicketReference repository=""
revision="585160586336f3bcd7b694f53cf10db73c56981c"
Fixed #36064 -- Skipped an UPDATE when adding a model instance with a
composite primary key with default values.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36064#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701944fd00d98-97e2d751-25cf-4d71-a431-4145a708f5ff-000000%40eu-central-1.amazonses.com.
