Changes between Initial Version and Version 14 of Ticket #14149


Ignore:
Timestamp:
Apr 28, 2017, 11:55:54 AM (7 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14149

    • Property Component UncategorizedDatabase layer (models, ORM)
    • Property Cc Erin Kelly Matt Boersma Andrii Kurinnyi tsawyer1 added
    • Property Summary Oracle backend - conflict between two ticketsLIKE clauses fail in Oracle 9.2.0.7
    • Property Has patch set
    • Property Triage Stage UnreviewedAccepted
    • Property Resolutionfixed
    • Property Status newclosed
    • Property Easy pickings unset
    • Property SeverityNormal
    • Property TypeBug
    • Property UI/UX unset
  • Ticket #14149 – Description

    initial v14  
    1 Hi,
     1I'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.
    22
    3   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.
     3I'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.
    44
    5   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.
    6 
    7  For the record, the database I'm connecting to is 9.2.0.7 (I know, old).
    8 
    9   Cheers
    10 
    11     Jirka
     5For the record, the database I'm connecting to is 9.2.0.7 (I know, old).
Back to Top