#21890: django.core.exceptions.FieldError: Local field ... in class ... clashes
with field of similar name from base class ...
----------------------------+---------------------------------------
Reporter: claus | Owner:
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-alpha-1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => fixed
Comment:
This has since been fixed by the autodetector rewrite. You will lose data
with this move, as it's a column being moved across tables; to avoid this,
you would have to manually create a migration that made the new column,
copied data across, and then removed the old column, and then gave the new
column the correct name (it can't have it to start with as it would clash,
like the original error here)
--
Ticket URL: <https://code.djangoproject.com/ticket/21890#comment:5>
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/063.de519c80934fb98a99077cc45db7c02b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
