#27530: Referencing a function in a model field definition, and then removing
that
reference (and function) after running a migration raises an exception
-------------------------------+--------------------------------------
Reporter: Jesse | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
This a [https://docs.djangoproject.com/en/1.10/topics/migrations
/#historical-models documented caveat] of historical models.
You can either can squash these migrations or copy your `upload_to`
function definition into the migration files referencing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/27530#comment:1>
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/067.055aa3f724e67568a3f505591c88be16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
