Gio.File.query_exists
Description: Reference for Gio.File.query_exists

### Virtual Method

# Gio Filequery_exists

#### Declaration [src]

    gboolean
    query_exists (
      GFile* file,
      GCancellable* cancellable
    )

#### Description [src]

Utility function to check if a particular file exists.

The fallback implementation of this API is using `g_file_query_info()` and therefore may do blocking I/O. To asynchronously query the existence of a file, use `g_file_query_info_async()`.

Note that in many cases it is racy to first check for file existence and then execute something based on the outcome of that, because the file might have been created or removed in between the operations. The general approach to handling that is to not check, but just do the operation and handle the errors as they come.

As an example of race-free checking, take the case of reading a file, and if it doesn’t exist, creating it. There are two racy versions: read it, and on error create it; and: check if it exists, if not create it. These can both result in two processes creating the file (with perhaps a partially written file as the result). The correct approach is to always try to create the file with `g_file_create()` which will either atomically create the file or fail with a `G_IO_ERROR_EXISTS` error.

However, in many cases an existence check is useful in a user interface, for instance to make a menu item sensitive/insensitive, so that you don’t have to fool users that something is possible and then just show an error dialog. If you do this, you should make sure to also handle the errors that can happen due to races when you execute the operation.

#### Parameters

`cancellable`

  Type: `GCancellable`

  Optional `GCancellable` object, `NULL` to ignore.

  The argument can be `NULL`.
  The data is owned by the caller of the method.

#### Return value

Type: `gboolean`

`TRUE` if the file exists (and can be detected without error), `FALSE` otherwise (or if cancelled).