pdb.simple_in, and generated cast helper names. Use the casts documented here instead of calling those helpers directly.
Most new queries should use the pdb schema. A smaller set of operational and lower-level functions lives in the paradedb schema.
Query Builders
Query builders return a ParadeDB query object for the right-hand side of@@@.
pdb.term, pdb.term_set, pdb.range, and pdb.range_term are overloaded for supported Postgres scalar and range types.
The aggregate form pdb.term_set(value bigint) still exists for compatibility, but new queries should use pdb.term_set(array_agg(...)) instead.
Query Modifier Casts
Modifier casts attach scoring, fuzzy, or slop settings to another query expression.Proximity Builders
These functions create proximity clauses for@@@.
The symbolic
## and ##> operators are usually more concise than these function forms.
Scoring and Highlighting
These functions are placeholders that ParadeDB’s custom scan resolves during query execution. Use them in queries that also contain a ParadeDB predicate.Aggregates
Supported aggregate JSON shapes are documented under Aggregates, including terms, range, histogram, date histogram, filters, sum, average, min/max, count, stats, percentiles, cardinality, and top hits.
Index Configuration and Tokenizers
The
fast parameter on paradedb.field is a compatibility name for columnar
storage. New index definitions should use tokenizer casts with the columnar
option where text or JSON fields need columnar storage.pdb.tokenize_simple, pdb.tokenize_icu, pdb.tokenize_ngram, and pdb.tokenize_edge_ngram. Prefer tokenizer casts or paradedb.tokenize(...); the generated helper names are part of the cast implementation.
Index Diagnostics and Maintenance
Related views:
Lower-Level SearchQueryInput Builders
Theparadedb schema exposes lower-level builders that return searchqueryinput directly. They are useful for compatibility and generated SQL, but new hand-written queries should usually prefer pdb.* query builders plus @@@.
Most
pdb.* query builders that target a single field also have a generated paradedb.*(field fieldname, ...) -> searchqueryinput counterpart. That includes parse_with_field, match, match_disjunction, match_conjunction, exists, fuzzy_term, term, term_set, range, range_term, phrase, phrase_array, phrase_prefix, regex, regex_phrase, proximity, and proximity_in_order.
Tokenizer Casts
Tokenizer configuration is usually expressed through casts when creating an index or issuing tokenizer-specific queries.Compatibility and Internal Functions
Olderparadedb.* scoring and highlighting names remain for backwards compatibility. Prefer pdb.score, pdb.snippet, pdb.snippets, and pdb.snippet_positions.
Generated type I/O functions, cast helpers, and planner support functions are implementation details. They may appear in
\df output, but they are not part of the recommended SQL surface.