#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 Marc Fargas <[EMAIL PROTECTED]>):
Replying to [comment:10 Marc Fargas <[EMAIL PROTECTED]>]:
> Just a side note, BinaryField will require maxlength (as it inherits
CharField) but PostgreSQL backend will '''ignore''' it.
> Related to this, you can use this BinaryField to store '''any''' amount
of data on PostgreSQL but only ''maxlength'' bytes on MySQL.
>
> The ticket is marked "needs documentation" so I'm writting it, I'll
write a note stating that ;)
If a binary field is provided it should allow the developer to decide
which amount of data does he/she want to store so in the case of
PostgreSQL maxlength could be enforced checking the length before saving
**and** it should not be limited to 64Kb, it should allow **any amount**
from 1 byte to the maximum field size (1GB on postgresql).
Also maxlength should be "maxbytes" ?
--
Ticket URL: <http://code.djangoproject.com/ticket/2417#comment:18>
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
-~----------~----~----~----~------~----~------~--~---
