Yeah, that would be safer. MULTI_THREADED still has the occasional issue (although some people seem to be using it without problems).
On 2014-03-10 22:16, Fabian Kessler wrote:
As a better alternative to MULTI_THREADED, do you still recommend to create multiple separate single connections to the same db in read-only non-locking mode, and managing these connections in something like a connection pool in the code? (I've read that suggestion from Thomas somewhere in the forum.)
-- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
