#22373: Django Migrations keeps detecting changes to FileField using custom
storage
-------------------------------------------+------------------------
Reporter: Matthias Pronk <django@…> | Owner:
Type: Bug | Status: new
Component: Migrations | Version: 1.7-beta-1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------------+------------------------
I've a FileField that uses a custom storage backend, which is a subclass
of FileSystemStorage. After adding a deconstruct function to my custom
storage backend, Django's migration framework keeps detecting that the
FileField has changed ad infinitum.
{{{
from django.core.files.storage import FileSystemStorage
class MediaStorage(FileSystemStorage):
def deconstruct(self):
return ('foo.media.storage.MediaStorage', [], {})
}}}
The migration file shows:
{{{
migrations.AlterField(
model_name='file',
name='file',
field=models.FileField(storage=foo.media.storage.MediaStorage(),
upload_to='foo_media/', max_length=255, verbose_name=u'file'),
),
}}}
Note: This bug is related to #22337, but not the same.
--
Ticket URL: <https://code.djangoproject.com/ticket/22373>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/076.f6bd0c28d77dc556e8236e05cac094f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
