#23983: Cannot Alter order_with_respect_to after there is already data in a
table
----------------------------+------------------------------------
Reporter: jpulec | Owner: coldmind
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by MarkusH):
I think we should set an initial ordering
(https://github.com/django/django/blob/aa5ef0d4fc67a95ac2a5103810d0c87d8c547bac/django/db/models/base.py#L1624-L1633)
. Otherwise upcoming saves will start to be ordered, while old data isn't.
The ordering of the existing data should be done by the default ordering
of the referenced model (`model._meta.ordering`)
--
Ticket URL: <https://code.djangoproject.com/ticket/23983#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.4c27f25efdeccf165b4fe9c30d8ff8bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
