Hi >From what I can see in the source code, H2 is using the normal java processes >for serialising and de-serialising Java objects before calling read() or write(). So you could either override serialisation using the normal means (readObject() and writeObject()) or you could serialise them yourself into byte[]'s.
Regards, Noel. choces wrote: > Hi, > > Would it be enough to convert the Object into a byte[] and back?. > I presume serialization of Objects would be well suited to populate > Blobs. I use it for storing images into a database. > > Regards, > Carlos Hoces > > On 20 sep, 08:09, Thomas Mueller <[email protected]> wrote: >> Hi, >> >> There is no feature to customize the serialize/deserialize behavior. It >> would be a nice addition I guess, patches are welcome. The feature could >> look like this: >> >> org.h2.util.Utils.serialize / deserialize: >> >> if (serializer != null) { >> return serializer.serialize(obj) / deserialize(data); >> >> } >> >> The serializer could be a static field whose class can be set using a system >> property. I know system properties are a bit an ugly API, but at the >> beginning it would be sufficient I guess. >> >> 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.
