#14149: Oracle backend - conflict between two tickets
---------------------------+------------------------------------------------
Reporter: JirkaV | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.2
Keywords: oracle | Stage: Unreviewed
Has_patch: 0 |
---------------------------+------------------------------------------------
Hi,
I've recently started using Oracle backend, connecting to a database I
don't own or operate. I started seeing behaviour described in #5985
(DatabaseError: ORA-01425: escape character must be character string of
length 1), fixed in r7412. Since I was hitting an issue that's been
apparently fixed, I started digging in history and found that the fix was
reverted in r12293 (related ticket: #11017). The fact that it might
reintroduce the bug is actually mentioned in the ticket.
I'm happy monkeypatching my Oracle base.py as I may as well be the only
person suffering from this issue these days. Mentioning it here mostly for
the record, if someone searches for it in future. I'm also happy to help
testing any suggested solutions if someone has an idea that would fix
#5985 without breaking #11017 again.
For the record, the database I'm connecting to is 9.2.0.7 (I know, old).
Cheers
Jirka
--
Ticket URL: <http://code.djangoproject.com/ticket/14149>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
