Hi, > Transaction Isolation = yes > Encrypted Database = yes > User defined datatypes = yes > Table Level Locking = yes > Multi Version Concurrency = yes > Updatable Result Sets = yes > Information Schema = yes > Custom Aggregate Functions = yes > Footprint (jar/dll size) = 1.19 megs
Thanks, I will update those. As for encrypted databases, HSQLDB (as well as Derby) doesn't hide data patterns well, see also http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Electronic_codebook_.28ECB.29 > Row Level Locking = yes As far as I see, it's the same behavior as H2: it's supported when using the MVCC mode. > The page should also have topics for multi-threading, access control, > durability, protocol encryption added they are important for many > users. I will add "Multi-Threaded Statement Processing" (not enabled in H2 by default, and not supported when using MVCC). > protocol encryption Isn't SSL/TLS supported by all databases? Regards, Thomas P.S. Why is H2 not included in the "benchmark" image on http://hsqldb.org ? -- 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.
