It's an old post but for anyone still searching i might have some insight about the viability of mvstore in android.
For the past year i've been using nitrite-db <https://github.com/dizitart/nitrite-database> which is a *nosql* db that uses mvstore. The library itself is fine but i always have issues with mvstore corrupting the db file. This mainly occurs during background operations (async tasks, threads, etc). After implementing multiple checks to not use the db if a thread is interrupted and making sure the db closes properly when the app closes i still get many crashes in the wild. So my verdict is that it's unfit for android, at least when dealing with background operations. -- 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.
