When trying to return a resultset using the DB2 Dialect it throws the following error: DB2Dialect does not support resultsets via stored procedures, however it is possible to get around this in 2 ways:
1) Don't include the callable="true" attribute on the <sql-query /> declaration.
2) Use the SQLServerDialect because DB2 UDB can return resultsets in a similar fashion to SQL Server.
Customer says that (1) is not correct, you do need callable=true, but that if you copy code from sql server dialect, SP queries work on DB2. So I've done that.
Max Rydahl AndersenApril 28, 2005 at 9:46 AM
but if callabled=false we dont do anything stored procedure specific handling....so this should actually work out of the box ?!
When trying to return a resultset using the DB2 Dialect it throws the following error: DB2Dialect does not support resultsets via stored procedures, however it is possible to get around this in 2 ways:
1) Don't include the callable="true" attribute on the <sql-query /> declaration.
2) Use the SQLServerDialect because DB2 UDB can return resultsets in a similar fashion to SQL Server.
The Exception is thrown from:
org.hibernate.dialect.Dialect#registerResultSetOutParameter