Hi, (1) Perhaps use byte[] as the basic key/value of your interface. > > I think it's a good point. Specially on Android ByteBuffer might be quite a lot slower than byte[]. I will definitely test it.
Usually you still will have to deserialize at least key to do comparisons > I'm not sure how this is related to using byte[] versus ByteBuffer. I would prefer avoid dealing with byte arrays at all and have an abstract > pluggable serialization/desrialization which will use > ObjectInput/ObjectOutput or something similar. > At some point the data has to be stored to disk, and the question is whether this should be done using a byte[] or a ByteBuffer. Files don't support ObjectInput/ObjectOutput as far as I know. > Also it would be nice to take into consideration that some types still can > be compared without full deserialization but some can't, so it should be > possible to do comparisons in the most effective way. > That's a good point, such features are missing currently. It is something to keep in mind. 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.
