# Prepare a useful Coordinator DB contribution

Start a Coordinator DB contribution with a concrete public behavior: the SQL or connection task, what currently happens and what should happen instead. For a bug, include a small schema and synthetic rows that reproduce it. For a documentation fix, name the page and the statement that needs correction.

A useful SQL report keeps setup and observation together:

```sql
CREATE TABLE contribution_example(id INTEGER PRIMARY KEY, value INTEGER);
INSERT INTO contribution_example VALUES (1, 10);
SELECT id, value FROM contribution_example WHERE id = 1;
```

Replace this example with the smallest case that demonstrates your issue. Include the exact error and expected result, and state whether the request used native TCP, HTTP or an embedded connection. Interface differences can be part of the behavior being reported.

Before proposing a fix, check the public reference so a missing feature is not mistaken for a regression. Keep changes focused on the stated behavior and include meaningful verification. Do not publish private data, credentials or unrelated operational output in a contribution.

Use the project's current contribution instructions for its submission procedure rather than assuming a particular review policy or release schedule.

See [SQL statements](https://coordinatordb.com/docs/reference/statements), [deployment modes](https://coordinatordb.com/docs/get-started/about/deployment-modes) and [installation](https://coordinatordb.com/docs/get-started/setup/install).