Search table rows and relationships

Sapporta table search has four independent responsibilities: table metadata defines the plan, callers supply a term, the server applies relationship-aware authorization, and the database executes the resulting predicates. Read only the page that owns the part you are changing.

• Configure table search covers default search, selected root columns, foreign-key labels, recursive child paths, disabling search, and configuration validation.
• Use table search covers the generated UI, HTTP, export, CLI, frontend, and application server callers.
• Relational search semantics and security explains literal term matching, predicate composition, generated SQL, and authorization on every relationship branch.
• Index relational search paths covers child-foreign-key indexes, query-plan review, and the point at which the generated substring search should give way to FTS or an external index.

Start with configuration when changing a table definition. Start with usage when composing a query against an existing table. Security-sensitive review should include the semantics page even when no metadata changes.

Related documentation

• Relationships and lookup behavior
• Filtering, sorting, search, and pagination
• Table and column metadata
• Row-scoped data helpers