Hi, > I'm sure its a bug.
In your view, yes, and I understand your view. My previous boss once said the definition of a bug is: it's where the documentation and the implementation don't match. In H2 it is not documented that the CALL statement returns a result set at http://h2database.com/html/grammar.html#call - but the CALL statement always did return a result set (with one row, or with many rows). Changing this behavior would probably break existing applications that rely on this current behavior. For H2, you can still use CallableStatement, call c.execute(), and then call c.getInt(). I understand the behavior of H2 doesn't match the behavior of other databases, but I'm afraid it's not something that I can change currently. I will add a feature request, and patches are welcome of course. Regards, Thomas -- 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.
