Hello, I have now fixed this issue (https://github.com/jOOQ/jOOQ/issues/3011) to work around sqljdbc_4.0's limitation. The fix will collect all SQLException's and put them into SQLException.getNextException() as is the expected behaviour. As I mentioned, the fix will be merged to 3.3.1 and 3.2.4.
Note that this issue did not appear with jTDS in the first place, so *I might need some more information to reproduce potentially new issues.* ---- On a side-note, while fixing this issue I have found traces of why Statement.execute() was called in the first place, instead of Statement.executeUpdate(). This is due to an issue when plain SQL is executed through Query.execute() instead of ResultQuery.fetch(), even if it returns result sets. A corner case in some JDBC drivers. More information here: https://github.com/jOOQ/jOOQ/issues/1829 Regards, Lukas 2014-02-18 16:33 GMT+01:00 Lukas Eder <[email protected]>: > Hi Venkat, > > 2014-02-18 15:21 GMT+01:00 Venkat Sadasivam <[email protected]>: > > Lukas - I spoke too soon. Still in some cases we do not get exception when >> raise error is thrown in trigger. >> > > Just to be sure, those raise error levels *are* above 10, right? > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
