I want to use H2's MVStore with a large number of objects (maps), many of which are derived from each other, often differing in a single property.
I'd like to write a plugin serializer that can write an object as a reference to another object plus a delta from that object. This would reduce storage but, more importantly, since I'm using Clojure's persistent data structures, it would mean a derived object would share most of its structure with its parent, greatly reducing heap usage. The serializer would need therefore to potentially access the H2 MVStore while reading an object, calling back 'up' the stack as it were to read parent object(s). This strikes me as an unexpected thing to do, and I wonder if H2 would have a problem with that? Another approach might be to store derived objects in a different map, so the serializer's access to it looks like just an another external access. Any feedback? Cheers, Matt. -- 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.
