#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: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Wael Ramadan):
Replying to [comment:9 Wael Ramadan]:
> Replying to [comment:8 Mariusz Felisiak]:
> > Replying to [comment:6 Wael Ramadan]:
> > > This has to be investigated as to what fixed the issue!
> >
> > It fails for me on the `main` branch, `stable/4.1.x` branch, and with
`4.1.2` version so it's definitely not fixed.
>
> How is that possible that it fails on `4.1.2` what type of database are
you using?
OK, oddly enough purged everything and started from scratch using `4.1.2`
and it does fail.
--
Ticket URL: <https://code.djangoproject.com/ticket/33945#comment:10>
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/01070183e65a9ddf-91edf966-53a6-4c83-8bd8-37679382679a-000000%40eu-central-1.amazonses.com.
