Another approach could be using existing Value classes first for Types.OTHER and do java serialization only when Value.convertTo(JAVA_OBJECT) is called, e.g. from org.h2.table.Column#convert. Seems the most straightforward way.
On Tuesday, March 29, 2016 at 2:25:14 PM UTC+6, Noel Grandin wrote: > > Yeah, I've been thinking I that adding an extra query to PreparedStatement > is a rather nasty performance hit when the client and server are not on the > same computer. > > I don't think we need a new Value subclass. We just need to find an > appropriate place (on the server side) to convert the incoming Value object > to something more appropriate. Not sure where that is right now. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
