[hdf-forum] How best to model objects that have lists of sub objects.

[Peter Alexander]

On Tue, Jun 23, 2009 at 2:12 PM, Dimitris Servis<servisster at gmail.com> wrote:
> Richard,
>
> mapping a C++ object tree to HDF5 objects is a thing I also had in mind to
> set up at some point. Neglecting the "resurrection" (instead of
> de-serialization) part of the tree where cyclic graphs can prove a
> nightmare.... what I do not seem to get right out of your approach is why
> you say "In this model, each 'A' object has it's own list of indexes to B
> objects". std::vector<B> is a container of B objects, therefore a dataset on
> its own, right? Wouldn't this look like:
>
> [A DATASET]
> data1, "DATASET REF A_B_1"
> data2, "DATASET REF A_B_2"
> data3, "DATASET REF A_B_3"
>
>
> [A_B_1 DATASET]
> B1
> B3
> B4
>
> [A_B_2 DATASET]
> B2
> B5
>
> [A_B_3 DATASET]
> B3
>
> I probably miss something?!?
>
> Peter,
>
> could you send a link to that 'Root' software package? 'Root' is a really
> bad name when googling....

I hope this helps us find an efficient and flexible model for object
persistence in consideration of the existing HDF5 data storage model.
ROOT is extremely interesting package.. I just wish it was HDF5 based
with object persistence as a secondary consideration.

http://root.cern.ch/drupal/

>
> Regards,
>
> -- dimitris
>
>

----------------------------------------------------------------------
This mailing list is for HDF software users discussion.
To subscribe to this list, send a message to hdf-forum-subscribe at hdfgroup.org.
To unsubscribe, send a message to hdf-forum-unsubscribe at hdfgroup.org.