#28222: QuerySet.update_or_create() field validation should allow settable
properties in defaults
-------------------------------------+-------------------------------------
Reporter: Alex Mykyta | Owner: Alex
| Mykyta
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: 1.11 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"b9abdd92ab21a796943e8047e778eebc671c8c00" b9abdd92]:
{{{
#!CommitTicketReference repository=""
revision="b9abdd92ab21a796943e8047e778eebc671c8c00"
[1.11.x] Fixed #28222 -- Allowed settable properties in
QuerySet.update_or_create()/get_or_create() defaults.
Backport of 37ab3c3f9d707d6a1896db79c631e920dcb1fb78 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28222#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.f349ffbd7b3a561d28b0f4b8a81427e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
