#34915: do not autopopulate _order field for model with an
order_with_respect_to if
already set
-------------------------------------+-------------------------------------
Reporter: Tilman | Owner: nobody
Koschnick |
Type: | Status: new
Uncategorized |
Component: Database | Version: dev
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
If a model has the Meta option "order_with_respect_to", new instances of
the model have the _order field autopopulated, no matter if the _order
field is already set or not. I propose to only set the field if it has not
previously been set already, allowing a custom order to be set before
saving new objects, and saving a query to the database in this case.
This will not affect existing code that does not explicitly set the _order
field before saving the object.
--
Ticket URL: <https://code.djangoproject.com/ticket/34915>
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/0107018b4c1cdbe9-c6ab65a4-0d6a-44e3-8551-321a64e4a826-000000%40eu-central-1.amazonses.com.
