Hi, > (1) getting it to work properly in a distributed environment > with multiple GAE application instances accessing the same database;
That will be hard, and in some cases it's the wrong solution... I guess a more scalable solution is to use 'linked tables' that are backed by the Google DataStore. But having a stable virtual file system backed by the Google DataStore will help others as well, not only H2. Files greater than 1 MB is the most important missing piece I think. Some kind of file locking support would be great. Currently H2 doesn't use file locking to ensure the database is only opened in one process, instead it uses it's own 'cooperative file locking' protocol. But regular file locking is relatively easy to add (in the class FileLock). > Is anyone interested in this? I'm interested, and I'm sure others are interested as well. 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 -~----------~----~----~----~------~----~------~--~---
