Hi, If the keys and values are individual byte[], then it wouldn't be performant. By default, the keys/values are objects of type java.lang.Object within a Page. If you write your own Page implementation it could even be int or long (anything).
The bigger question is what the serialization format is before the values are stored to / read from a file, and what file level abstraction should be. For a byte[], it could be a RandomAccessFile, and for ByteBuffer it could be a FileChannel. Of course a byte[] can be wrapped within a ByteBuffer. Currently ByteBuffer is used, and I think I will keep this unless it is a performance problem for Android, and if it is probably switch to my own wrapper around byte[], similar to Data currently used in H2. Regards, Thomas On Fri, Sep 7, 2012 at 9:51 PM, wburzyns <[email protected]> wrote: > I definitely second the idea of having byte[] as keys/values. It's as > universal as it could be. > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/h2-database/-/m5ZDR2XgFCcJ. > > 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. > -- 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.
