#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version:
Resolution: fixed | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by avk):
* status: assigned => closed
* resolution: => fixed
Comment:
Replying to [comment:55 [email protected]]:
> Is this the expected behaviour?
I agree that for a consistency reasons there should be always one type
returned, probably 'buffer',
since PostgreSQL developers mention that it is more efficient in this use
case. I will try to fix
it for all databases again so we will have consistent behavior.
Meanwhile, I would like to mention that from usage standpoint there is no
big difference between two types:
str can be converted to buffer, and buffer can be converted to 'str' when
required, using functions str(buffer)
or buffer(str).
--
Ticket URL: <http://code.djangoproject.com/ticket/2417#comment:56>
Django <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
-~----------~----~----~----~------~----~------~--~---
