Thank you Evgenij for clarification. This helps a lot. We will give an attempt with H2 1.4.199 in memory first, then plan to do file storage. Batch insert would help us a lot, reduce the number I/Os to SD card, in some scenarios emmc storages. For us, SQL is more expressive, flexible and easy to generate them at runtime, we hope for best for the data and data aggregation requirements.
MVStore still a good library for to store our configuration files ie JSON content with compression and encryption. We don't need any queries for the same. On Tue, Apr 23, 2019 at 9:48 AM Evgenij Ryazanov <[email protected]> wrote: > Hello. > > Standalone MVStore is not a database at all. It's just a copy-on-write > key-value storage with multiple maps and optional transactions (with > TransactionStore). Of course, you can iterate over MVMap from MVStore by > your own code and perform some computations, but I guess it's not that you > want. > > If you need database capabilities, such as SQL queries with aggregate and > window functions you need to use a database, such as H2 1.4.199 or some > other (PostgreSQL, MySQL 8.0, latest versions of SQLite, etc.) > > -- > 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. > -- 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.
