dirfile_rename (3) - Linux Manuals

dirfile_rename: change the name of a dirfile field


dirfile_rename --- change the name of a dirfile field


#include <getdata.h>
int dirfile_rename(DIRFILE *dirfile, const char *old_code, const char *new_name, int move_data);


The dirfile_rename() function changes the name of the field specified by old_code, which should not contain a representation suffix, defined in the dirfile specified by dirfile to new_name. If the new name is the same as the old name, this function does nothing.

When renaming a metafield, the metafield should be specified in old_code by its full (slashed) field code, while new_name should only contain the new name (without slash).

If the flag move_data is non-zero, and old_code specifies a RAW field, the binary file associated with the field will be renamed as well. If move_data is zero, no changes will be made to the binary file. If field_code specifies a field of type other than RAW, the move_data flag is ignored.


On success, dirfile_rename() returns zero. On error, -1 is returned and the dirfile error is set to a non-zero error value. Possible error values are:
The specified dirfile was opened read-only.
The library was unable to allocate memory.
The field specified by old_code was not found.
The supplied dirfile was invalid.
An attempt was made to rename the immutable INDEX field.
The representation suffix specified in field_code was not recognised.
The new name specified is already in use by another field.
The metadata of the format file fragment containing the field was protected from change, or the binary data of the fragments was protected from change and binary file translation was requested.
An I/O error occurred while attempting to rename the binary file.
The encoding scheme of the specified field could not be determined or was not understood by GetData.
The encoding scheme of the field does not support binary file renaming. The dirfile error may be retrieved by calling get_error(3). A descriptive error string for the last error encountered can be obtained from a call to get_error_string(3).