On 2019/08/29 7:01 AM, areichel wrote:
1) would it not be possible to throw a more meaningful exception, e.g. "Failed to allocate table space"
We generally do, in fact we have unit tests that check that, but obviously we missing something. Very hard to get error handling right everywhere, especially for the edge cases.
2) why do especially indexes and constraints consume so much space in H2?
H2, by default in the latest versions uses a storage engine that trades off space for improved IO speed. You can switch to the older (and more compact) storage engine by append MV_STORE=FALSE to the URL.
3) Is the a way to use compression when writing the H2 database file? I would like to use the H2 merely as a container for transporting data (instead of Schema dumps) and I wounder if a GZIP/BZIP stream could be used to write a compressed file.
H2 is not well suited to that use-case. You'd be better off with one of the schema/data SQL dump tools floating around. But we do have some options for compressing the data. http://h2database.com/html/advanced.html#file_system -- 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/d2d3221f-e7b3-4d89-c67a-e0510713a7c7%40gmail.com.
