Am Freitag, 20. November 2015 17:59:21 UTC+1 schrieb Dieter Blerms: > > > So what happens when closing the DB that the file size increases from 29 > MB to 47 MB? > > I think i found out what happens: as the tables are cached tables, the index tables are stored in memory and after closing the db they will be stored (for persistence).
Is this right? I was just wondering, why the DB size is so much bigger as for mySQL (there the size of the closed DB is 25 MB - dump size is about 15 MB). The Java-App I'm writing shall be an offline version of a php-website. The (read-only) db access there is the mySQL database. The Java-App should be as small as possible and run on Linux, Windows and Mac. I wanted to keep the migrated H2-db in memory for faster db queries. Now i think it would be better to keep it as a embedded, file based db and just keep the query-results in memory. Sorry for all this. I'm new to H2 and similar db-systems. regards Dieter -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
