Hi, The class is this one https://github.com/nicolas-f/H2GIS/blob/h2spatial-osgi-snapshot/h2spatial/src/main/java/org/h2spatial/ValueGeometry.javathere is only JTS Geometry inside. The serialised data should be restricted to Well Known Binary.
Using Externalizable the class identifier and some other bytes are still stored in bytes value. I don't understand why we need to store the serializer on each value. The idea is to use the same serializer on each value of the column (then retrieve the serializer class on the metadata of the column) A more complex solution is to implement CREATE TYPE<http://docs.postgresqlfr.org/8.1/sql-createtype.html>instruction.. -Nicolas 2013/5/16 Thomas Mueller > 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.
