#23983: Cannot Alter order_with_respect_to after there is already data in a
table
----------------------------+------------------------------------
Reporter: jpulec | Owner: coldmind
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: fixed
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 Tim Graham <timograham@…>):
In [changeset:"10482faf1996e654cb9849d7c0065841ad2adf35"]:
{{{
#!CommitTicketReference repository=""
revision="10482faf1996e654cb9849d7c0065841ad2adf35"
[1.7.x] Fixed #23983 -- Fixed a crash in migrations when adding
order_with_respect_to to non-empty table.
Backport of 3dbbb8a89ca4beaabd5359fe82e32ed633b15140 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23983#comment:8>
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.f6843ec64c90e50de10fd4557e2630b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
