#36100: get_next_by_FIELD() check for unsaved objects should account for
composite
primary keys
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"1602666b79ab438930b74b576f2fa1b6bcf0377b" 1602666]:
{{{#!CommitTicketReference repository=""
revision="1602666b79ab438930b74b576f2fa1b6bcf0377b"
Fixed #36100 -- Checked if composite pk is set in get_next/get_previous.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36100#comment:3>
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/010701946ac73f78-c5442ac6-47d7-4682-948c-9d10c96aee53-000000%40eu-central-1.amazonses.com.
