#36093: Calling `full_clean()` on an existing child model instance in a
multi-table
inheritance should not execute a database query.
-------------------------------------+-------------------------------------
Reporter: Sage Abdullah | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sage Abdullah):
I have a sneaking suspicion that the problem may also manifest in the
other areas affected by the commit, e.g. `bulk_update`. I have yet to
confirm it, though.
If handling this requires some additional logic to check whether a field
is a primary key beyond checking its existence in `_meta.pk_fields`, we
might need to have a dedicated method for it and use it everywhere.
--
Ticket URL: <https://code.djangoproject.com/ticket/36093#comment:1>
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/010701946068f5af-b972232d-ce1a-43d3-9df5-657fde10c13e-000000%40eu-central-1.amazonses.com.
