Escaping bug exists in Oracle 9.2.0.5 and earlier. It was fixed in patchset 9.2.0.6 and any later version.
What comes to Oracle official support options for 9.2: Premier Support Ends: 31-Jul-2007 Extended Support Ends: 30-Jul-2010 If any problem is encountered you're first required to upgrade to latest patchset (9.2.0.8) before requesting further assistance from Oracle. And Oracle has always advised to apply patchsets to db. I have only 9.2.0.1, but bug should appear there and I've patchsets for 9.2.0.6 and up so I can see does it really happen after upgrade. I can stage and run tests to see was it that or something else. And known workaround (that works "everywhere") is use one I pasted few ticket comment before. It's more like design and support decision here - is there need to support (obsolete) Oracle version(s)? -- Jani Tiainen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
