Missing:
One should find a way how to check which driver is used and if ms sql, run the proper version of the query - in DbExecutionServerImpl.java. So it seems that the issue is just with the query in DbExecutionServerImpl.java, otherwise fixed.
From Paul: From what I remember the main problem I had was a small diff in the SQL usage (LIMIT vs TOP) and the position of that definition in the SQL query. I couldn't find an easy way to get the persistent level to make a distinction based on the JDBC driver (I didn't know enough on that level to convert it into a proper fix). Other than that it did work though.
tomas-knap
commented
7 years ago
Missing:
One should find a way how to check which driver is used and if ms sql, run the proper version of the query - in DbExecutionServerImpl.java. So it seems that the issue is just with the query in DbExecutionServerImpl.java, otherwise fixed.
From Paul: From what I remember the main problem I had was a small diff in the SQL usage (LIMIT vs TOP) and the position of that definition in the SQL query. I couldn't find an easy way to get the persistent level to make a distinction based on the JDBC driver (I didn't know enough on that level to convert it into a proper fix). Other than that it did work though.