#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: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?
--
Ticket URL: <https://code.djangoproject.com/ticket/33945#comment:9>
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/01070183e6298e5c-e65d9d5f-c836-4a18-9271-9266b2f94e99-000000%40eu-central-1.amazonses.com.
