Opened 9 years ago
Last modified 9 years ago
#25866 new Cleanup/optimization
Django migrations not picking up max_length change on FileField — at Version 1
Reported by: | Gerben Morsink | Owned by: | nobody |
---|---|---|---|
Component: | Migrations | Version: | 1.7 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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"
Note:
See TracTickets
for help on using tickets.