#25866: Django migrations not picking up max_length change on FileField
-------------------------------------+-------------------------------------
Reporter: gabn88 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by gabn88):
* needs_docs: => 0
* needs_tests: => 0
* needs_better_patch: => 0
Old description:
> I have a FileField which first had no max_length
>
> Now I changed max_length to 1000. Then running ./manage.py makemigrations
> it does not seems to be picked up
New description:
I have subclassed a FileField (call it S3storage) which first had no
max_length
Now I changed max_length to 1000. Then running ./manage.py makemigrations
it does not seems to be picked up.
The only thing I did was:
class S3FileField(models.FileField):
def __init__(self, *args, **kwargs):
super(S3PrivateFileField, self).__init__(*args, **kwargs)
self.storage.default_acl = "private"
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25866#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 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/064.8dda25a657f79d97a0505fc96ac7c7a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
