Hi, > This is not a performance issue, this is field size cost issue.
I see. What is the class of the object? If it's "your own" class, then I think the serialization could be user defined, or (maybe better) we could use Externalizable (which would also require a change in H2, but it should be straightforward). Your proposal (that the serializer class is set when declaring the column) works well but I think it requires one field (the serializer) per value. This is a slight memory usage disadvantage. I just like to understand if there are any alternatives, but maybe this is the best solution. > H2Spatial pass all OGC SFS Conformance test (53 unit tests), I will add some additional unit test then spatial index. That's really great! Thanks a lot! 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.
