>>>>> " " == elias collas <[EMAIL PROTECTED]> writes:
[snip]
> 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:
Or you could just store the file name in an pytables Group
attribute. Then it would be a simple matter of creating a wrapper for
pytables.openFile() which would open the file, walk the Groups and
mount any files coresponding to attributes where you save the mount
points. This way clients would just have to call an alternate open
function.
Of couse, if you are using a server to control access to the file or
something like cstables, then the file would always be open and client
scripts would not even have to know about mounted files. This is what
I'm wanting to do.
Mike Romberg
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/pytables-users
