#13296: order_with_respect_to fails to correctly track _order after deleting
entries
-------------------------------------+-------------------------------------
Reporter: Chris | Owner: Hasan
| Ramezani
Type: Bug | Status: closed
Component: Database layer | Version: 1.1
(models, ORM) |
Severity: Normal | Resolution: fixed
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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"2362f2726558dd0cc6e447878545dd3ddbd9b633" 2362f272]:
{{{
#!CommitTicketReference repository=""
revision="2362f2726558dd0cc6e447878545dd3ddbd9b633"
[3.0.x] Fixed #13296 -- Fixed ordering by Options.order_with_respect_to
after deleting objects.
Thanks Simon Meers for the original patch.
Backport of f97bbad908df128189eff77d98af9a25ed1ecf23 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/13296#comment:13>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/066.fbe1c39d2dbc20c91b069c9955124c40%40djangoproject.com.
