Yesterday, I told you about my ordeal with the Oracle JDBC Driver and the cryptic Non supported SQL92 token at position: x message I was getting.
Turns out that the problem was that when running the script in Continuous Integration builds, embedded SQL92 syntax escape processing was enabled by default.
In the end, the solution was to turn off escape processing so that code behaviour is the same whether run via Continuous Integration or as a standalone SQL script in SQL Developer.
In conclusion, I still think the guys at Oracle should implement better error messages, as this would have saved me loads of time.
Be well.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment