Ok, to wrap up: For 1:1 key:value mapping I should use unique hashed constriant and memory table to keep indexes in the memory.
One two questions about MEMORY TABLE (http://www.h2database.com/html/ grammar.html#createtable) a) Are data within the MEMORY TABLE safe? What if anything bad occurs? If I understand correctly H2 should start up and recreate index automaticaly, there should be no data loss. b) Where can I manage memory consumation of the MEMORY TABLE index? I mean indicies will not be stored in the main cache (CACHE_SIZE setting), right? If I use DB in the embedded mode I think I will not like H2 to eat all the heap. :-( Thank you very much for the support and help. LZ On 21 čvn, 13:25, Thomas Mueller <[email protected]> wrote: > Hi, > > > SET UNDO_LOG 0 - turns off undo log (I do not need rollbacks) > > SET LOCK_MODE ? > > SET LOG ? > > I wouldn't disable the undo log, unless you have very large > transactions. Also, I wouldn't change the other settings unless you > fully understand what those mean - see the documentation for more > information. > > > Clustered indices are designed for that sort of thing, but AFAIK H2 doesn't > > support that yet; maybe when the new page store scheme is implemented? > > Yes, that's the plan. Clustered indices should be easy to add once the > "page store" is done. > > > settings ... for optimizing queries on large tables > > Sorry, I don't think there are settings that would help. > > Regards, > Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. 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 -~----------~----~----~----~------~----~------~--~---
