Hi, Currently, the easiest way to plug a different storage engine is using 'linked tables'. Linked tables over JDBC are already supported. Since a long time I plan to use this mechanism to support the Google App Engine (meaning, store data on the Google App Engine data store). Unfortunately, the plan is still a plan; so far it never was a high enough priority. Thanks to Vince Bonfanti, H2 actually does run on GAE now, using GaeVFS - but there are many limitations (due to H2, not due to GaeVFS).
Basically you would need to write additional 'Table' implementations similar to TableLink, TableLinkConnection, LinkedIndex. The transaction log of H2 would still be used, I'm not sure what's the best solution there, specially if transactions span multiple storage engines. Maybe use two phase commit? Not sure if all storage backends support that. Something unrelated: I like LINQ. And I like Scala. Did you have a look at my simple OR mapping tool JaQu? http://www.h2database.com/html/jaqu.html - I'm almost sure if this idea is ported to Scala you could write code that looks almost like LINQ. Or even SQL. Without sacrificing the advantages of Scala (type safety, autocomplete, protected from code injection,...). A new feature I recently added (just a prototype currently) is the 'Natural Syntax' that uses 'Java closures' and parses that by decompiling the bytecode. Not sure if that would be required for Scala. > H2... it's now the default database for new Lift projects. Good to know! 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.
