Coordinator DB use cases ​

Choose a use case by the result a reader needs and the changes the application must make. The examples in this section use documented SQL behavior and make their data assumptions explicit. They do not imply an automatic external connector, managed service or background refresh process.

For exact identifiers and small records, start with key-value lookups. Primary keys and upserts express how repeated keys should behave. For dated measurements, use the time-series guide, with explicit timestamp and retention rules.

For operational events, log analysis combines typed columns with optional JSON attributes. For embeddings already supplied by an application, vector comparisons show fixed-dimensional values and distance functions.

A task can combine these patterns, such as filtering events by account before grouping their counts. Validate joins and result cardinality before interpreting a report. Pick the connection mode according to session lifetime and file ownership, then measure representative queries through that same interface.

See deployment modes, types and SQL statements.