On 02/12/10 15:40, Jirka Vejrazka wrote:
I'm using Django against an Oracle 10 database. It used to work. Then they
upgraded it to 10.2.0.5 (not sure what from, I can probably find out).
Hi Tim,
sorry, I don't have a solution for you, but you might want to check
out http://code.djangoproject.com/ticket/14149 and add description of
your environment there so there is more "use cases" listed there.
Actually, I do have a solution - I do monkeypatch the Oracle backend
so it matches my version of Oracle (i.e. 2 or 4 backslashes).
Cheers
Jirka
P.S. This got me thinking - maybe the Oracle backend could do some
"autodetection" of which version works fine in the current
environment? Yes, it'd be extra query at startup I guess, but don't
really see any other way...
Thanks for that.
Interesting that I'm seeing this in an upgrade from 10.2.0.4 to 10.2.0.5.
Instead of changing from LIKE to LIKEC - if I add more backslashes will
that work?
Cheers,
Tim.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
