Skip to:
Previously I could execute StoredProcedures using this:
After upgrading to Hibernate 5.3.1.Final the Database driver throws the error:
I found a workaround by using
and inside `work.execute(Connection connection)` method before doing the same as previously calling `connection.setCatalog("otherdb");`
As demonstrated by the test cases in this commit, the problem comes from the SQL Server JDBC Driver, not from Hibernate.
So, ordinal-based parameter binding works just fine:
while name-based parameter binding does not:
There's nothing to be fixed in Hibernate ORM about this issue. The SQL Server Driver should support both parameter binding methods.
Notice that the name-based parameter binding works just fine across schemas. It just does not work across catalogs.
Previously I could execute StoredProcedures using this:
After upgrading to Hibernate 5.3.1.Final the Database driver throws the error:
I found a workaround by using
and inside `work.execute(Connection connection)` method before doing the same as previously calling `connection.setCatalog("otherdb");`