On Mon, Mar 22, 2010 at 11:22:00PM +0100, Wildam Martin wrote:
Who cares. I am using H2 because a) I can embed it in my Java apps without loosing platform independence b) it is fast c) small size It seems, both reasons would be destroyed with the C-Version.
I'm a little confused here. Why would the existence of a 'C' version of H2 destroy the Java version? The Java version isn't going away. Personally, having a 'C' version of H2 that operated on the same database files as the Java version would take an already useful and powerful database an greatly extend its reach and applicability. The JVM isn't a perfect solution for everything, mostly for the reasons Thomas gave, it's large and has a slow startup. For example, it becomes painful to use for something like command-line utilities. SQLite is not really a full SQL implementation. It is missing a lot of features. There are also some common scenarios where it's performance degrades immensely, where H2 does much better. Perhaps a useful first step would be a C client that allows connections to the backend running in a JVM. This would allow for short-lived, fast starting clients, and only require a subset of the code to be working. David -- 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.
