I have a database which uses mvstore directly (no sql).  It has three maps 
in it, one of which is only ever loaded when I create the database.  I 
always close the database between writing this first table and subsequent 
runs when I am just reading the table. The other two tables are written and 
read.  

In all cases I do not need the data read from the database cached for 
re-read, as I convert the data read from the database into internal 
structures which I keep anyway.

Is there any way to tell mvstore that my first table is readonly after the 
first run, and will it help?

Also is there a way to tell mvstore not to bother caching read results, and 
again will it help?

-- 
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 h2-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/68527411-5671-4a27-b5d3-7900c9380f91n%40googlegroups.com.

Reply via email to