I think the answer is "no" on both points. Currently here is no API to declare particular map read-only, and there is no way to disable caching of data for particular map, since it cached at lower level. I wonder what benefits do you expect from that?
On Tuesday, December 20, 2022 at 3:28:54 PM UTC-5 [email protected] wrote: > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/9fd6f87c-e1d1-478d-ace6-98332bbf56a6n%40googlegroups.com.
