#34915: Do not autopopulate _order field for model with an
order_with_respect_to if
already set.
-------------------------------------+-------------------------------------
Reporter: Tilman Koschnick | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Uncategorized => New feature
* has_patch: 1 => 0
* resolution: => wontfix
Comment:
Thanks for this ticket, however, I don't understand why you want to set
ordering with respect to the given field and in the same time set it
manually. It seems that you should use your own custom logic for ordering
and disable `order_with_respect_to`. The proposed behavior would be
confusing and counterintuitive.
You can start a discussion on DevelopersMailingList if you don't agree,
where you'll reach a wider audience and see what other think.
--
Ticket URL: <https://code.djangoproject.com/ticket/34915#comment:1>
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/0107018b4c2f094a-663b8ae1-ceb5-4675-9496-77e2c333b485-000000%40eu-central-1.amazonses.com.
