Hi, I realized that I ran my last tests with the old /PreparedStatement.setCharacterStream()/ instead of /PreparedStatement.setString()/. It seems that removing both /setCharacterStream()/ usage and connection pooling the db size doesn't increase. So I have shared at https://gist.github.com/davidecavestro/6283789 a standalone test case that *sometimes reproduces* the issue. It creates a database into the temp folder and then drops and inserts some data. It uses a DataSource that proxies h2 JdbcConnection instances with a custom class. Relaunching it more two or three times you can see it generates some errors on the trace file, and the database size starts to increase.
-- View this message in context: http://h2-database.66688.n3.nabble.com/h2-Continuous-Increase-in-H2-db-size-after-dropping-and-loading-same-data-repeatedly-tp4026836p4027196.html Sent from the H2 Database mailing list archive at Nabble.com. -- 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.
