#36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a
more
appropriate exception
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
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:"46b3e7dd8cc1792a40bb8b4d0c267f3d1ceef68c" 46b3e7dd]:
{{{#!CommitTicketReference repository=""
revision="46b3e7dd8cc1792a40bb8b4d0c267f3d1ceef68c"
Fixed #36048 -- Preferred ValueError to NotSupportedError for composite pk
sanity checks.
These checks are not backend-dependent.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36048#comment:4>
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/010701943abf705c-16aff095-89d9-48e3-be0c-74a06156f1d1-000000%40eu-central-1.amazonses.com.
