Can BlazeSQL keep an answer it just gave a user?
BlazeSQL saves an answer and its query, then reopens the saved item with the same three rows under the saved name. The saved item appears in a separate Saved area, and the reopened table matches the earlier chat answer.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Saved answer reopened in a new sessionPassEvidence
“Show me our monthly order count for the last 3 months, as of September 2, 2026.”
Monthly Order Count Last 3 Months month order_count 01/06/2026 16 01/07/2026 26 01/08/2026 47 There's a clear upward trend over the last 3 months! 📈 • June: 16 orders • July: 26 orders • August: 47 orders Order volume nearly tripled from June to August. Would you like to visualize this or dig deeper into any specific month?
Copied from Proof 1 · Output file (text), lines 26–39
Open the text file ↗Its contents are printed above, under What the tool returned.
Open the text file ↗| ✓ | Expected: Reopening should show the same answer and make it clear it is the same saved question.Found: The saved item reopened as 'Scenario 54 table' and showed the same three rows; the saved name identifies it. |
The answer and query were saved, reopened from Saved under the chosen name, and the reopened table showed the same three rows as the chat answer.
Save scope. Saving keeps the answer and its query, not the full conversation.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the row says which and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the row says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Reporting → | |
| Scenario | The user wants to keep an answer they just got → | |
| Tool | BlazeSQL → |
Global scenario definition → · Global capability definition → · BlazeSQL product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.