Opened 10 years ago
Last modified 10 years ago
#23996 new New feature
Allow AlterOrderWithRespectTo to order existing data
Reported by: | Markus Holtermann | Owned by: | |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Markus Holtermann | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (7)
comment:1 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 10 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 10 years ago
comment:4 by , 10 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
comment:5 by , 10 years ago
Easy pickings: | unset |
---|
@mhall1, you probably didn't realize since you marked the ticket as "Accepted" it doesn't appear in the unreviewed ticket queue to get feedback. Anyway, the ideas seems okay to me although I am not quite sure what the implementation would look like -- would the questioner iterate through all the rows and ask for an order # or something else?
comment:6 by , 10 years ago
I suggest to order the existing rows by the default ordering of the related model (the owrt is defined on).
I apologize but I have to release this ticket because I'm leaving on vacation and its still waiting for approval by the core team.