Basic types
FQL has seven built-in value types:
| Type | Example | Description |
|---|---|---|
NONE |
NONE |
Represents an absent or undefined value. |
bool |
true, false |
Represents a truth value. |
number |
42, 3.14 |
Represents numeric values, both integer and floating-point. |
string |
"hello" |
Represents text. |
array |
[1, 2, 3] |
Represents an ordered sequence of values. |
object |
{ name: "Ada" } |
Represents a set of named fields. |
binary |
module-specific | Represents raw bytes. |
Ferret hosts may also define additional value types — documents, elements, HTTP responses, files, handles, database connections, and other external resources. These are called host values and are covered separately in Host Values.
NONE
NONE is Ferret’s equivalent of null, nil, or None in other languages.
It represents the absence of a value.
NONE is a real value in FQL. It can be assigned to variables, placed inside arrays and objects, returned from functions, and compared with other values.
Unlike SQL NULL, comparing with NONE does not automatically produce another NONE.
NONE is useful when a value is intentionally absent:
It is useful when that absence needs to remain distinct from ordinary values such as false, 0, "", [], or {}.
Booleans
Boolean values represent truth values.
FQL has two boolean values:
truefalse
Booleans are commonly produced by comparison operators, logical operators, predicates, and conditions.
Boolean values can be combined with logical operators:
Numbers
FQL uses the number type for numeric values. Numbers can be written as integers or decimals:
Numbers support arithmetic operations:
They can also be compared:
Numbers are ordered by numeric value:
1 < 210 > 2-1 < 0
Numeric-looking strings are still strings. FQL does not treat "10" as the same value as 10.
Use explicit conversion functions when a script needs to turn text into a number or a number into text.
Strings
Strings represent text and can be written as quoted literals:
Strings can be empty:
An empty string is still a text value, not the absence of a value. It is different from NONE.
Strings are commonly used for names, labels, URLs, selectors, extracted text, keys, and identifiers.
Strings can be compared with other strings. Comparisons use the string contents, so two strings are equal when they contain the same sequence of characters.
String comparisons are always case-sensitive.
Arrays
Arrays are ordered collections of values written with square brackets:
Arrays can contain any FQL value:
Arrays preserve the order of their elements.
Array items can be accessed by index using bracket notation:
An empty array represents a collection with no items:
An empty array is not the same as NONE.
Arrays are commonly produced by FOR loops and collection operations.
Array elements can be nested:
Objects
An object is an unordered collection of named values, written with curly braces:
Each object entry has a property name and a value, which can be any FQL value.
Object properties can be accessed with dot notation or bracket notation.
Use dot notation when the property name is known ahead of time:
Use bracket notation when the property name comes from a string literal or variable:
Because objects do not preserve key order, property order does not affect object equality. Two objects with the same properties and values are equal, even if those properties were written in a different order.
An empty object represents a record with no properties:
An empty object is not the same as NONE.
Binary values
Binary values represent raw bytes.
They are used for data that should be handled as bytes instead of ordinary text, such as downloaded files, encoded payloads, images, archives, or data exchanged with runtime modules.
Binary values are part of the FQL value model, but they are usually returned by functions, modules, or runtime operations. For example, an HTTP, file, or encoding module may return binary data when the result should be treated as bytes.
Type checks
Scripts often receive values in different shapes. Use type-related functions or predicates when logic needs to branch based on the kind of value being handled.
Type checks are useful when working with external data, optional fields, runtime-backed values, or module results.
See the Standard Library section for the full list of available type-checking functions.