#24443: Changing upload_to on a filefield creates a migration despite not
changing
the database at all
---------------------------------+--------------------
Reporter: gregplaysguitar | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------
upload_to is commonly set in django settings, and changing the setting
generates a "Your models have changes that are not yet reflected in a
migration..." warning until you create an (effectively no-op) migration.
This really shouldn't trigger a migration, because upload_to is solely
used to generate a file path, and doesn't change the underlying field at
all.
It's not much of a problem for local apps, you just end up with extra
migrations, but it happens with 3rd-party apps too.
--
Ticket URL: <https://code.djangoproject.com/ticket/24443>
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/058.573ebd4766f3dcf2dda8991ed8ebbc38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
