Hi, Most people are of the opinion that H2 is not durable and hence not > fully ACID compliant compared to even Derby, apart from MySql, > Postgress etc. >
If you read the H2 documentation in more detail, you will notice that Derby and other databases are also usually not 100% durable in the event of a power failure due to operating system and hardware limitations (there are some exceptions: when using special hard disks, and disable write caching in the operating system / file system). For H2, the default settings are different than in other databases, but the performance tests were run with the same durability for all databases where available. But best if you read the relevant documentation at http://h2database.com/html/advanced.html#durability_problems In H2 it is recommended that use SET WRITE_DELAY and CHECKPOINT SYNC. > But more examples are needed along with cause and effect > relationship. > > Can anyone elaborate? > I suggest to read the documentation and come back if you have specific questions. 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.
