A Dimecres 15 Febrer 2006 14:56, Stefan Kuzminski va escriure: > I am writing code that manages a set of tables in a single node. Take > for example the case of deleting a columns from a table. I was planning > on writing a new table ( minus the dropped column ) to a 'temporary' > node in the HDF, and then move ( using moveNode ) that new table back > over the original table. My question is, is this an efficent > operation? Is there a better way?
Yes, moveNode is the best way in the sense that it only moves pointers to the data in datasets, not the data itself. It is the equivalent of a 'mv' in Unix. Of course, if you are using moveNode between files, then, a copy of the data is made (in the same way than a 'mv' between different filesystems). Cheers, -- >0,0< Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data "-" ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Pytables-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pytables-users
