Query Syntax

FsPulse provides a flexible, SQL-like query language for exploring scan results. This language supports filtering, custom column selection, ordering, and limiting the number of results.

Query Structure

Each query begins with one of the four supported domains:

roots
scans
items
changes

You can then add any of the following optional clauses:

DOMAIN [WHERE ...] [SHOW ...] [ORDER BY ...] [LIMIT ...]

Column Availability

`roots` Domain

All queries that retrieve root information begin with the keyword roots:

roots [WHERE ...] [SHOW ...] [ORDER BY ...] [LIMIT ...]

Property	Type
`root_id`	Integer
`root_path`	Path

`scans` Domain

All queries that retrieve scan information begin with the keyword scans:

scans [WHERE ...] [SHOW ...] [ORDER BY ...] [LIMIT ...]

Property	Type
`scan_id`	Integer
`root_id`	Integer
`root_path`	Path
`scan_time`	Date
`is_hash`	Boolean
`hash_all`	Boolean
`is_val`	Boolean
`val_all`	Boolean
`adds`	Integer
`modifies`	Integer
`deletes`	Integer

`items` Domain

All queries that retrieve item information begin with the keyword items:

items [WHERE ...] [SHOW ...] [ORDER BY ...] [LIMIT ...]

Property	Type
`item_id`	Integer
`scan_id`	Integer
`root_id`	Integer
`item_path`	Path
`root_path`	Path
`file_size`	Integer
`file_hash`	String
`val`	Validation Status
`val_error`	String
`mod_date`	Date
`item_type`	Item Type Enum

`changes` Domain

All queries that retrieve change history begin with the keyword changes:

changes [WHERE ...] [SHOW ...] [ORDER BY ...] [LIMIT ...]

Property	Type
`change_id`	Integer
`scan_id`	Integer
`item_id`	Integer
`root_id`	Integer
`item_path`	Path
`root_path`	Path
`file_size`	Integer
`file_hash`	String
`val_old`	Validation Status
`val_new`	Validation Status
`val_error_old`	String
`val_error_new`	String
`mod_date_old`	Date
`mod_date_new`	Date
`item_type`	Item Type Enum
`change_type`	Change Type Enum
`meta_change`	Boolean

The `WHERE` Clause

The WHERE clause filters results using one or more filters. Each filter has the structure:

column_name:(value1, value2, ...)

Values must match the column’s type. You can use individual values, ranges (when supported), or a comma-separated combination. Values are not quoted unless explicitly shown.

Type	Examples	Notes
Integer	`5`, `1..5`, `3, 5, 7..9`, `null`, `not null`, `NULL`, `NOT NULL`	Supports ranges and nullability. Ranges are inclusive.
Date	`2024-01-01`, `2024-01-01..2024-06-30`, `null`, `not null`, `NULL`, `NOT NULL`	Use `YYYY-MM-DD`. Ranges are inclusive.
Boolean	`true`, `false`, `T`, `F`, `null`, `not null`, `NULL`, `NOT NULL`	Values are unquoted. Null values are allowed in all-lower or all-upper case.
String	`'example'`, `'error: missing EOF'`, `null`, `NULL`	Quoted strings. Null values are allowed in all-lower or all-upper case.
Path	`'photos/reports'`, `'file.txt'`	Must be quoted. Null values are not supported.
Validation Status	`V`, `I`, `N`, `U`, `null`, `not null`, `NULL`, `NOT NULL`	Valid (V), Invalid (I), No Validator (N), Unknown (U). Unquoted. Ranges not supported.
Item Type Enum	`F`, `D`, `null`, `not null`, `NULL`, `NOT NULL`	File (F), Directory (D). Unquoted. Ranges not supported.
Change Type Enum	`A`, `D`, `M`, `null`, `not null`, `NULL`, `NOT NULL`	Add (A), Delete (D), Modify (M). Unquoted. Ranges not supported.

Combining Filters

When specifying multiple values within a single filter, the match is logically OR. When specifying multiple filters across different columns, the match is logically AND.

For example:

scans where scan_time:(2025-01-01..2025-01-07, 2025-02-01..2025-02-07), hashing:(T)

This query matches scans that:

Occurred in either the first week of January 2025 or the first week of February 2025
AND were performed with hashing enabled

The `SHOW` Clause

The SHOW clause controls which columns are displayed and how some of them are formatted. If omitted, a default column set is used.

You may specify:

A list of column names
The keyword default to insert the default set
The keyword all to show all available columns

Formatting modifiers can be applied using the @ symbol:

item_path@name, mod_date@short

Format Specifiers by Type

Type	Allowed Format Modifiers
Date	`full`, `short`, `nodisplay`
Path	`full`, `relative`, `short`, `name`, `nodisplay`
Validation / Enum / Boolean	`full`, `short`, `nodisplay`
Integer / String	(no formatting options)

The `ORDER BY` Clause

Specifies sort order for the results:

items order by mod_date desc, item_path asc

If direction is omitted, ASC is assumed.

The `LIMIT` Clause

Restricts the number of rows returned:

items limit 50

Examples

# Items whose path contains 'reports'
items where item_path:('reports')

# Changes involving validation failures
changes where val_new:(I) show default, val_old, val_new order by change_id desc

See also: Interactive Mode · Validators · Configuration