Ask for a SQL in plain language, but verify before running
Recipe template · not yet tested on this site
This page is a recipe template, not yet tested here. Run logs, tokens and time go in after re-testing; until then no estimated numbers are filled in.
When to use
You want to query a table but don't want to hand-write SQL, and fear a generated statement might drop the db or query wrong.
Preparation
- Host version
- To fill (record the exact rc version when testing)
- Model
- To fill
- Mode / permissions
- Standard mode + modify-within-workspace is enough to start
- Plugins required
- None (add name & version after testing if used)
- Input materials
- Keep in a separate workspace; back up originals first
Full instruction
Generate one SQL from the need below. Query only, no data modification.
Table schema (columns, types, constraints): [paste schema or CREATE TABLE]
Need: [one sentence describing what to query]
Requirements:
1. Restate your understanding of the schema and the need; wait for my confirmation before giving SQL.
2. No UPDATE / DELETE / DROP / TRUNCATE / INSERT in the SQL.
3. Pre-run checklist: full-table scan? oversized result? are all column names present in the schema?
4. If ambiguous, list both interpretations and let me choose; don't guess.
5. Add a rough estimate of expected row count.Run log
| Item | Value | Note |
|---|---|---|
| Time spent | to be tested | |
| Result | to be tested | |
| In / out tokens | to be tested | |
| Leftovers | to be tested |
Output
After a successful run, list files and screenshots here, and note whether originals changed.
Acceptance checklist
Tap to tick each item off as you verify.
- SQL contains queries only, no writes
- Column names come from the provided schema
- Ambiguities list multiple interpretations
- A pre-run checklist is given
Failures & boundaries
- Have a human review before running on a real db; generated results are not guaranteed
- Confirm join keys for multi-table queries
- This is a recipe template and has not been tested on this site
- Blocked on: Needs a real schema and real data distribution. Without them the generated SQL can be syntactically right and semantically wrong, making any conclusion worthless.