#9893: Filename + path length greater than 100 truncated on database insertion
in
Core.Storage
-------------------------------------+--------------------------------------
Reporter: Refefer | Owner: nobody
Status: new | Milestone: 1.2
Component: Core framework | Version: SVN
Resolution: | Keywords: storage, filename
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by jacob):
* milestone: 1.1 => 1.2
Comment:
I think ultimately akaihola's idea of modifying the `get_valid_name` and
`get_available_name` to accept a max length is the right way to go. Using
a text field is a bad idea for a bunch of reason -- speed, storage size,
compatibility with Oracle -- but any hardcoded length could possibly be
too short.
At this point past feature-freeze, though, changing that signature could
cause too much heartache. I'm going to punt this to 1.2; for now, it's a
simple workaround: use `FileField(max_length=SOMETHING_BIGGER)`.
--
Ticket URL: <http://code.djangoproject.com/ticket/9893#comment:8>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
