#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: assigned | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by Simon G. <[EMAIL PROTECTED]>):
This looks good, and we'd like to get this in. However, the patch needs a
few improvements (and tests!) if possible (see the discussion in the list
thread I linked above). First, it should not subclass CharField, and it
will need to maintain database portability (do we need to transparently
store everything in base64 here?). Finally, we should increase the size of
this (not to store huge blobs of data, but larger than 255 bytes - 64kb is
enough?)
--
Ticket URL: <http://code.djangoproject.com/ticket/2417#comment:17>
Django Code <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 [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?hl=en
-~----------~----~----~----~------~----~------~--~---
