#9893: Filename + path length greater than 100 truncated on database insertion
in
Core.Storage
-------------------------------------+-------------------------------------
Reporter: Refefer | Owner: Pavel
| Shpilev
Type: Bug | Status: closed
Component: File | Version: master
uploads/storage |
Severity: Normal | Resolution: fixed
Keywords: storage, filename | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jan Geboers):
Hello,
could it be that this bug still exists?
Both on Django 1.8.18 and 1.11.2 I see this behavior isn't corrected yet.
The validation of max_length takes only file_name into account and ignores
upload_to, causing truncation on the database level, exactly as described
in https://code.djangoproject.com/ticket/13314
When I check out the relevant code I strongly suspect this bug was never
fixed:
https://github.com/django/django/blob/master/django/forms/fields.py#L553
--
Ticket URL: <https://code.djangoproject.com/ticket/9893#comment:46>
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/065.ee2eaa58a531a3bb92afbaa604b81c13%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
