yes, application can ignore and JDBC allows not to read the result. However, I have a generic mechanism in my application that always reads the result. So, in my case I'll have to do some workaround for this specific case. And the worst thing is that, it looks I cannot distinct when to read it and when not, since i need both options available and it is basically should be the user's choice, who controls the SQL. So, an option in the H2 function would be preferable in my case.
On Friday, July 31, 2020 at 4:16:22 PM UTC+3 Evgenij Ryazanov wrote: > I don't see any good reasons for such modifications in H2. Result of this > function can be ignored by application. JDBC doesn't require you to read > result of a query. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/dabbc35d-e594-4278-b00e-5fba4fcac45an%40googlegroups.com.
