Expand description

Defines the fields used in the query result structs

Structs

The field corresponding to the ctime_f field. ctime is the last inode change time measured in floating point seconds (including the fractional portion) since the unix epoch.

The field corresponding to the ctime field. ctime is the last inode change time measured in integer seconds since the unix epoch.

The field corresponding to the content.sha1hex field. For regular files this evaluates to the sha1 hash of the file contents.

The field corresponding to the cclock field. the cclock is the created clock; the clock value when we first observed the file, or the clock value when it last switched from !exists to exists.

The field corresponding to the dev field. The dev field is the device number expressed as an integer. This field is not meaningful on Windows.

The field corresponding to the exists status of the file

The field corresponding to the type field. The type field encodes the type of the file.

The field corresponding to the ino field. The ino field is the inode number expressed as an integer. This field is not meaningful on Windows.

The field corresponding to the mtime_f field. mtime is the last modified time measured in floating point seconds (including the fractional portion) since the unix epoch.

The field corresponding to the mtime field. mtime is the last modified time measured in integer seconds since the unix epoch.

The field corresponding to the mode field. This encodes the full file type and permission bits. Note that most programs and users are more comfortable with this value when printed in octal. It is recommended to use FileTypeField if all you need is the file type and not the permission bits, as it is cheaper to determine just the type in a virtualized filesystem.

The field corresponding to the name of the file.

Use the NameOnly struct when your desired field list in your query results consist only of the name field. It is not possible to use the query_result_type! macro to define an appropriate type due to limitations in the Rust macro system.

NewFieldDeprecated

The field corresponding to the new field. The new field evaluates to true if a file is newer than the since generator criteria.

The field corresponding to the nlink field. The nlink field is the number of hard links to the file expressed as an integer.

The field corresponding to the oclock field. the oclock is the observed clock; the clock value where we last observed some change in this file or its metadata.

The field corresponding to the gid field. The gid field is the owning gid expressed as an integer. This field is not meaningful on Windows.

The field corresponding to the uid field. The uid field is the owning uid expressed as an integer. This field is not meaningful on Windows.

The field corresponding to the size field. This represents the size of the file in bytes.

The field corresponding to the symlink_target field. For files of type symlink this evaluates to the result of readlink(2) on the file.