#9893: Filename + path length greater than 100 truncated on database insertion
in
Core.Storage
-------------------------------------+--------------------------------------
Reporter: Refefer | Owner: streetcleaner
Status: assigned | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords: storage, filename
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by akaihola):
Replying to [comment:6 wwinham]:
> What are the drawbacks to just making a FileField use Text instead of
varchar in the database? It seems like a pretty simple solution that would
completely resolve the issue.
Another point from Shai Berger in the [http://groups.google.com/group
/django-developers/browse_thread/thread/e6dd904a3f5a507b googlegroups
thread] mentioned earlier:
> In many engines, text fields are kept out-of-table; then, what's kept in
the
> table, is (effectively) the name of a file where the text is kept. Even
if
> this doesn't seriously affect performance, using such a field to keep a
> filename must raise a few eyebrows.
--
Ticket URL: <http://code.djangoproject.com/ticket/9893#comment:17>
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-upda...@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.
