I am trying to understand H2's durability and how to get improved durability for certain transactions. In general I think that the default durability of H2 is quite appropriate for my use case (knowing that in a rare crash I could lose about one second of data). But there are certain transactions that I would like to flush directly to disk.
By putting ACCESS_MODE_DATA=rws in a connection url, does that only affect the this connection or does that affect all connections? If it only affects this connection, then I think could use 'rws' followed by a CHECKPOINT SYNC to get specific transactions to flush. Would this work on specific transactions while running most everything else in default mode? Are there any other suggestions on how to use the default durability, and then also have the ability to flush specific transactions? Thanks, -Adam -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/LzTrO3uPujIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
