#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: Accepted
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:"9fa4d07ce0729850661a31a6b37c6b48f13d2266" 9fa4d07]:
{{{#!CommitTicketReference repository=""
revision="9fa4d07ce0729850661a31a6b37c6b48f13d2266"
Refs #36064 -- Added Model.has_db_default() to encapsulate NOT_PROVIDED
checks.
This avoids many awkward checks against NOT_PROVIDED and provides symmetry
with Field.has_default() which is also the reason why it wasn't made a
property.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36064#comment:9>
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/010701944f1febc8-bd81a23f-ba66-466e-9a22-a1499487d3ec-000000%40eu-central-1.amazonses.com.
