#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Keywords: binary type field
---------------------------------+------------------------------------------
I have a need of having fields that store small blips of binary
information. In general this works fine with the CharField, however it
will not work for all such fields. For example a datum that is just the
NUL character, or a series of NUL characters. With postgres at least:
"Character strings disallow zero octets,"
These are not things like images or other such large amounts of data. They
are typically fairly short (10 to 200 bytes).
For my purposes I created a small patch that adds a new field type that
basically is a CharField except it uses the binary type on postgres and
mysql.
Does the django project plan on supporting a binary type field, if so
should I post my patch for this?
--
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
-~----------~----~----~----~------~----~------~--~---
