- int gd_move(DIRFILE *dirfile, const char *field_code, int new_fragment, unsigned int flags);
If the new fragment has different affixes, the field will be renamed as part of the move. See gd_rename(3) for details on field renaming. The field is closed before moving, resulting in it's I/O pointer being reset to the beginning-of-field.
The flags parameter should be zero or more of the following flags, bitwise or'd together:
- By default, if the move results in a change of name for the field due to differing fragment affixes, ALIAS entries pointing to this field will be updated with the field's new name. Specifying this flag prohibits this behaviour, turning these aliases into dangling aliases. If moving the field doesn't rename it, this flag is ignored.
field, the binary file associated with the field will be translated to account
for the possibly different encoding, endianness, and frame offset of the
new format specification fragment. It will also be moved to a new directory, if
If this flag is not specified, no changes will be made to the binary file. If field_code specifies a field of type other than RAW, this flag is ignored.
If the binary file is translated, and the frame offset of the destination fragment is larger than that of the source fragment, this will result in permanent deletion of data from the database. If the new frame offset is smaller than the old frame offset, the binary file will be padded at the front with zeroes.
- Skip updating entries which would be invalid (see gd_rename(3) for details). By default, an invalid field causes the move to fail. If moving the field doesn't rename it, this flag is ignored.
If moving the field renames it, update entries which use this field as an input
to account for the new name (see
If moving the field doesn't rename it, this flag is ignored.
RETURN VALUEOn success, gd_move() 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 field_code was not found, or else the move resulted in the field being renamed and the resultant metadata update tried to change a field code into something prohibited by a fragment's affixes.
- The supplied dirfile was invalid.
- An attempt was made to move the immutable INDEX field.
- The new_fragment argument did not index a valid format specification fragment.
- An I/O error occurred while attempting to translate a binary file.
- The metadata of the source or destination format specification fragments was protected from change, or the binary data of the source or destination fragments was protected from change and binary file translation was requested.
- The encoding scheme of the source or destination fragment is unknown.
- The encoding scheme of the source or destination fragment does not support binary file translation.