>
> What you are suggesting, I think, is something like:
> mountpoint = file1.mountFile('/common', file1.root._v_attrs.commom)
>
> for having access to the shared file in file1.root.common.
>
> Mmm, now that I think more about this, I'm not so sure that the later
> approach would be much better than the former. Do you envision some
> important advantage for the "mount thing"?.
>It may be that I don't understand exactly what H5Fmount is doing. If the mount has to be done dynamically, ie, at runtime, then there may be no advantage if the common filename has to be stored as an attribute. The advantage would be if an external file could be mounted in advance and made to persist, then the advantage would be that the client scripts wouldn't have to manage separate files and handles. Another solution may be to have a simple python configuration file for each database that simply points to each external file: # database1.conf common = "/path/to/shared.h5" results1 = "/path/to/run1.h5" # database2.conf common = "/path/to/shared.h5" results2 = "/path/to/run2.h5" etc. I suppose this is one of the nice things about Python, eh? So many possibilities... Elias Collas Stress Methods Gulfstream Aerospace /******************************************* * "You keep using that word. I do not * think it means what you think * it means." * -- Inigo Montoya *******************************************/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
