On Tuesday, May 2, 2017 at 10:56:26 PM UTC+2, [email protected] wrote: > > In regards to the retry option mentioned, is that just added to the URL > like this? > > "jdbc:h2:retry:./dbfilename;" > > Yes. That seems to be the format.
I just ran into this issue... first thought that H2 1.4 is simply broken and not ready to be used yet and then—with luck—found this issue. I use H2 as embedded database in an application with UI. And to dynamically react to user input, I use Thread.interrupt() all the time (basically canceling database reads that are not needed anymore). I expect H2 to respond gracefully to such interruptions. That is, throw a SQLException (I think that happened in 1.3) or something comparable. IMHO the current default behavior is not desirable and should be changed. Or is there a common scenario in which I would want to close the whole database for all threads when a single thread is interrupted—a perfectly normal thing to happen in all kinds of applications, but especially apps with UI? It seems that changing the current default behavior could certainly reduce the WTF-factor. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
