#33594: order_by("field1__-field2") yields inconsistent behavior
-------------------------------------+-------------------------------------
Reporter: Thomas Chaumeny | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
`"foo__-created_at"` it's not intended, documented, or officially
supported. It works by coincidence. I also cannot reproduce `FieldError`
after adding an index in `Meta.indexes`, I'm nor sure how adding an index
can interrupt ordering 🤔. There is something wrong in the described
models. Once `created_by` is a field on `SomeModel` and once on `foo`.
Can you double-check and provide a reproducible scenario?
--
Ticket URL: <https://code.djangoproject.com/ticket/33594#comment:2>
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/0107017fb19bcd75-e3230f3e-e8b5-4e1d-9c72-00ecff9eee22-000000%40eu-central-1.amazonses.com.
