#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]):
Could we consider using LARGE_BLOB as the default type for MySQL (and
ado_mssql, I guess), so that there's not a 64k limit on the size, by
default. I realize your application is specifically for small bits of
binary data, but if there's only going to be one binary type, it should be
as flexible as possible.
Also, I'm not sure about extending CharField. As I mentioned in an email
to django-developers, that means you show up in the admin, and I have to
agree with Malcolm that it's probably not a good thing to just display
random binary data. I'm not sure what the best way to allow binary input
is, but maybe using hex, as you mentioned in the patch, is an option. At
any rate, I'm not sure BinaryField should inherit from any currently
defined field type.
--
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
-~----------~----~----~----~------~----~------~--~---
