There are various possibilities: (1) Don't use SET LARGE_TRANSACTIONS TRUE
(2) Very large result sets i.e. more than 100000 bytes, which you could workaround by increasing the MAX_OPERATION_MEMORY setting
(3) Reading BLOBs from the database for which I don't have a workaround. Honestly, based on various bugreports floating around the webm it looks like the only long-term solution is for us to - remove our use of deleteOnExit - store entries in a global list and remove them from the list if we do actually delete the temp file - create our own shutdown handler to delete the files remaining on the global list on VM exit Patches welcome :-) -- 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/d/optout.
