General Coordinator DB questions ​

Coordinator DB stores relational data, validates declared types and lets applications query and change rows with SQL. Start by choosing the reader task: a keyed lookup, a grouped report, a joined query or a transactional change. The same product can serve different tasks, but each should be checked against its documented public interface.

A first connection can verify SQL execution without creating application data:

SELECT 1 AS connected FORMAT csv;

Then create a small table and exercise the types, constraints and query shapes your task needs. A successful connection alone does not prove every syntax extension or external integration is available.

General questions often depend on connection scope. A native connection retains its selected database and open transaction. HTTP requests each have a separate session. An embedded connection opens a file or an in-memory database directly and does not expose server-only commands.

Use the FAQ directory for specific questions, use cases for examples and operations for running a service. Keep feature claims tied to the statement reference.