Opened 11 years ago
Last modified 11 years ago
#24368 closed Uncategorized
FileField needlessly serializes upload_to — at Version 1
| Reported by: | Roman Odaisky | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.7 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
django.db.models.fields.FileField explicitly includes upload_to in the serialization process. This takes no part in the actual migration process but causes errors if the value of the field is a lambda function. Instead, the deconstruct() functions for FileField and other fields should only serialize arguments relevant to subsequent ALTER commands issued to the DBMS.
Once fixed, #22351 can be reverted.
Change History (1)
comment:1 by , 11 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | FileField needlessly serializes upload_to; same problems with some other fields → FileField needlessly serializes upload_to |
Note:
See TracTickets
for help on using tickets.