#10224 closed (fixed)
Oracle backend: raw binary field breaks
Reported by: | aprilmay | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Keywords: | oracle binary raw | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Support for raw binary Oracle can be useful when interfacing django with an existing database.
In db/backends/oracle/base.py such field wrongly falls back to unicode decode.
See attachment for a possible simple fix (the decoding of the binary data is then left to the application, possibly using binascii.b2a_hex).
Attachments (1)
Change History (3)
by , 16 years ago
Attachment: | django-oracle-binary.diff added |
---|
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Note:
See TracTickets
for help on using tickets.
(In [9821]) Fixed #10224: Don't attempt to decode binary string data in the Oracle backend.