LIKE clauses fail in Oracle 9.2.0.7
— at Version 14
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).
Change History
(15)
| Component: |
Uncategorized → Database layer (models, ORM)
|
| Cc: |
Erin Kelly Matt Boersma added
|
| Summary: |
Oracle backend - conflict between two tickets → LIKE clauses fail in Oracle 9.2.0.7
|
| Cc: |
Andrii Kurinnyi added
|
| Has patch: |
set
|
| Triage Stage: |
Unreviewed → Accepted
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
| Description: |
modified (diff)
|
| Easy pickings: |
unset
|
| Severity: |
→ Normal
|
| Type: |
→ Bug
|
| UI/UX: |
unset
|
Argh! I'm really starting to hate this issue. The underlying Oracle bug that was uncovered in #11017 is supposed to have been fixed in 9.2.0.6. I've tested it myself in 9.2.0.8 and am reasonably confident that the current implementation works there. I'm flummoxed as to what might be causing it in your scenario.