This is not a performance issue, this is field size cost issue. Using standard Java serialization the field contain additional information like class identifier and some other useless data. This is not blocking, I currently use JavaObjectSerializer however this is the same object serializer for all Java fields.
H2Spatial pass all OGC SFS Conformance test (53 unit tests), I will add some additional unit test then spatial index. Thanks for support. On Wednesday, May 15, 2013 7:29:40 PM UTC+2, Thomas Mueller wrote: > > Hi, > > Is this change needed for it to work, I mean, is it blocking you? It > sounds like a potential performance optimization, however I'm not sure if > it makes sense to change H2 at this stage. Couldn't you use regular > serialization? If serialization is really the (performance) bottleneck, we > could do this. > > Regards, > Thomas > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
