#33945: get_previous_in_order and get_next_in_order return incorrect data when
objects is stored in non-default database
-------------------------------------+-------------------------------------
Reporter: François Granade | Owner: Wael
| Ramadan
Type: Bug | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Wael Ramadan):
* status: new => closed
* resolution: => worksforme
Comment:
Using Django 4.1.1 this does actually fail. Yet when using Django 4.1.2
this works perfectly. Yet looking at the Release notes
(https://docs.djangoproject.com/en/4.1/releases/4.1.2/) there seems to be
no mention of this ticket.
This has to be investigated as to what fixed the issue!
--
Ticket URL: <https://code.djangoproject.com/ticket/33945#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183e2a0f7a5-810304dc-6bc4-4323-b654-8ec050d59284-000000%40eu-central-1.amazonses.com.
