[Django] #20879: BinaryField doesn't work with Oracle on Python3

14 views
Skip to first unread message

Django

unread,
Aug 8, 2013, 8:54:39 AM8/8/13
to django-...@googlegroups.com
#20879: BinaryField doesn't work with Oracle on Python3
-------------------------------------+-------------------------------------
Reporter: slafs | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.6-beta-1
(models, ORM) | Keywords: BinaryField Oracle
Severity: Normal | Python3
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
I made a repo as a showcase of this bug https://bitbucket.org/slafs/test-
django-binaryfield-oracle-py3

The test case in this repo is taken from Django testsuite.

The exception i'm getting is this:
{{{
django.utils.encoding.DjangoUnicodeDecodeError: 'utf-8' codec can't decode
byte 0xfe in position 2: invalid start byte. You passed in b'\x00F\xfe'
(<class 'bytes'>)
}}}

The problem is with handling Oracle params in
`django.db.backends.oracle.base.OracleParam` class. I think I may have a
solution on this.

--
Ticket URL: <https://code.djangoproject.com/ticket/20879>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Aug 8, 2013, 7:39:06 PM8/8/13
to django-...@googlegroups.com
#20879: BinaryField doesn't work with Oracle on Python3
-------------------------------------+-------------------------------------
Reporter: slafs | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version:
(models, ORM) | 1.6-beta-1
Severity: Normal | Resolution:
Keywords: BinaryField Oracle | Triage Stage:
Python3 | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shai):

* cc: shai@… (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0


Comment:

Hi, and thanks for your report.

I am looking forward to seeing what you come up with. Please also specify
exactly which Python3 and Oracle versions you are working with -- there
are known Unicode problems related to bugs in certain versions of Oracle
(#20292).

Also, you should be aware that Oracle under Python3 is generally broken
(#20725), so the problem may lie deeper than you think.

--
Ticket URL: <https://code.djangoproject.com/ticket/20879#comment:1>

Django

unread,
Aug 16, 2013, 8:51:07 AM8/16/13
to django-...@googlegroups.com
#20879: BinaryField doesn't work with Oracle on Python3
-------------------------------------+-------------------------------------
Reporter: slafs | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version:

(models, ORM) | 1.6-beta-1
Severity: Normal | Resolution:
Keywords: BinaryField Oracle | Triage Stage: Accepted
Python3 | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):

* type: Uncategorized => Bug
* stage: Unreviewed => Accepted


--
Ticket URL: <https://code.djangoproject.com/ticket/20879#comment:2>

Django

unread,
Jun 13, 2014, 10:02:42 PM6/13/14
to django-...@googlegroups.com
#20879: BinaryField doesn't work with Oracle on Python3
-------------------------------------+-------------------------------------
Reporter: slafs | Owner: nobody
Type: Bug | Status: closed

Component: Database layer | Version:
(models, ORM) | 1.6-beta-1
Severity: Normal | Resolution: fixed

Keywords: BinaryField Oracle | Triage Stage: Accepted
Python3 | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by shai):

* status: new => closed
* resolution: => fixed


Comment:

Some related fixes were introduced in #22715. The Django test-suite passes
on 1.7 and master with python3 and cx_Oracle 5.1.3; so I suspect this has
been solved.

If this is not the case, please reopen.

--
Ticket URL: <https://code.djangoproject.com/ticket/20879#comment:3>

Reply all
Reply to author
Forward
0 new messages