What does H2's on-disk format look like, and how does that tie-in with crash resilience? Could a power outage or JVM crash result in torn pages being written and the entire database refusing to launch afterwards (or spending hours processing WAL entries, uncertain about when or even if it'll ever finish)?
I really like MySQL's MyISAM in that respect. Yes you'll lose some data with it if it crashes and there's no WAL and no ACID and no nothing, but at the same time you'll only be losing a few rows around the affected spots rather than the entire table, because MyISAM doesn't use pages. How does H2 compare to this? -- 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.
