#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Type: enhancement | Status: assigned
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution:
Keywords: binary type field |
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
There could be potential issues here. There should be some sort of
support for setting the maximum size that a file can be that gets inserted
into this field to prevent a DOS issue by uploading multiple large items.
The BYTEA column can contain any size data (see
[http://www.postgresql.org/docs/8.1/static/datatype-binary.html]).
Would be great if this could be used for ImageField as well. Maybe
instead of adding a new field type, allow the user to set the "backend"
that Django uses to store the file. When set to Binary it would create a
new table to hold the binary objects, then a ForeignKey relationship
between the table that contains the metadata for the binary object, and
the the table which just contains the binary object itself. Deciding
whether to update the binary information in the binary table could be done
as the result of an md5sum hash or some other form.
--
Ticket URL: <http://code.djangoproject.com/ticket/2417>
Django <http://code.djangoproject.org/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
