Hi Thomas,
> That's interesting. I have tested H2 with the Android Emulator, but I > have no idea how H2 compares to SQLite on the actual device. Do you > have some experience about that? > I've worked around the problem of using the h2 compressed database in Android, by using the InputStream.read in the IOUtils.skipFully (instead of InputStream.skip). It worked, but the performance is too slow compared to the SQLite. I don't know whether it's caused by the overhead of using compressed database or because of other factors. I haven't tried using the normal h2 database with android. I've tried using the h2 compressed database in desktop environment, and I find the performance is pretty impressive. If the h2 engine can work with the same performance in android with compressed db, it will be terrific. Even more ideal is if you can have a build of h2 only as a query engine (SELECT only), which will reduce the size of the h2 jar to give even smaller footprint to be deployed. A lot of apps need only read access to the db, especially in resource-restrictive environments. So, android + h2 query engine + compressed db, will be a great solution for many applications targeting resource-restrictive devices, such as android. > So it sounds like this is a bug in the Android implementation? I don't think it's a bug. I think it's by design. Wrapping the Zip in a RandomAccessFile probably can give better performance than streaming in some cases. Cheers, Ricky --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-database@googlegroups.com To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
