According to the change log of 1.3.158, there had been a change like
this
* A Java function that returns a result set that was generated using
the
provided connection could cause an internal error in some cases.
Now such result sets are copied early on.
I suspect, this change has introduced a few regressions, which I have
documented here:
http://code.google.com/p/h2database/issues/detail?id=333
http://code.google.com/p/h2database/issues/detail?id=334
The reason for these regressions is the fact that prior to 1.3.158,
stored procedures returning RESULT_SET could return an actual
JdbcResultSet, which is the same type as returned from a regular
query. Now, the results seem to be copied to a SimpleResultSet, which
lacks some functionality.
I'll inform you if I should discover more regressions related to that
topic.
Cheers
Lukas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
