WhoDBDocs

Get useful answers from Chat

A useful Chat answer starts with a question whose meaning is clear enough to check. State the records and business rule you need, inspect the generated query, and compare the result to something you already know.

Describe the result precisely#

Include the object, relevant fields, filters, grouping, order, and limit when you know them. For example:

Text

Count orders for each user. Include users with no orders.
Return the user ID, username, and order count, highest count first.

Explain terms such as active, paid, or revenue if they have a particular meaning in your system. A model cannot reliably infer whether your team includes cancelled orders or which timestamp defines a reporting period.

Begin with a small read request when learning a schema. It is easier to check a few individual records than to diagnose an unexpected total from a large join.

Verify the query#

Open the generated SQL and check its tables, joins, and conditions. Compare a known record to the answer. For aggregates, inspect whether a join creates several rows for one business record and whether a date boundary includes the intended period.

When a query is correct, move it to Scratchpad for further checks and save it outside browser storage if it will be reused. Keep the definition of the result with the SQL.

Review proposed changes#

Read the statement in the execution card before approving it. Confirm the connection, target records, and values. A model's explanation is not proof that the statement is a read or that a write has a narrow scope.

If the target is unclear, cancel the proposal and inspect a read of those records first. See Review changes proposed by Chat.

Choose the data boundary#

Prompts, schema context, and included data can reach the configured model endpoint. Choose a provider and deployment appropriate for that data. Check the provider's current retention and usage terms directly rather than treating a local UI as evidence that requests stay local.

For setup or failed responses, see Provider setup and Chat troubleshooting.

Was this page helpful?