Hmmm, sorry, I don't have a quick fix for this.
It appears that the problem is not so much with getCharacterStream() as it is with setCharacterStream().
If you could make your ORM use the setString() calls, the shutdown, and in fact performance as a whole should improve.
On 2013-08-12 17:56, davide.cavestro wrote:
I confirm that values for CHAR, VARCHAR and LONGVARCHAR columns are set and read through /CharacterStream/s. Basically we have a proprietary ORM that maps every String-related column read and write respectively to /ResultSet.getCharacterStream() /and /PreparedStatement.setCharacterStream()/ calls .
-- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
