#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
-------------------------------------+-------------------------------------
Reporter: scanner@… | Owner:
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: reopened => new
* owner: nobody =>
* has_patch: 0 => 1
* version: => master
Comment:
I recently worked on this feature, and put the result in a pull request:
https://github.com/django/django/pull/597
Note that I choose to add only one type of field, as only MySQL has
different sized blob fields, and I don't think the few spared size bytes
are worth the trouble the creation of a dedicated field.
I didn't test at all on Oracle.
I'd love to get some feedback about this. I can imagine it does not cover
all of the possible use cases, but hopefully it covers the basic ones. We
can always improved things later.
--
Ticket URL: <https://code.djangoproject.com/ticket/2417#comment:76>
Django <https://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 https://groups.google.com/groups/opt_out.
