Does BlazeSQL keep a saved report current after new rows are added?
BlazeSQL kept the saved report current after new rows were added. The fixed-date save rose from 52 to 55, and the relative 30-day save rose from 162 to 164.
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 is based on this test case.
Saved report re-run after new rowsPassEvidence
Input 1: “Show me the number of orders placed in the last 30 days, as of September 2, 2026.”
Input 2: “Show me the number of orders placed in the last 30 days.”
Response 1 is the query the tool generated for Input 1; it is not part of the answer.
Response 2 answers Input 1.
Response 3 is the query the tool generated for Input 2; it is not part of the answer.
Response 4, the final response, answers Input 2.
order_count 162
Transcribed from Proof 3 · Screenshot
Every message the tool sent, in order (4)
- Generated query for input 1 · not part of the answer
SELECT COUNT(*) AS order_count FROM public.orders WHERE placed_at >= '2026-08-03' AND placed_at <= '2026-09-02 23:59:59'; - Response to input 1 (message 2 of 2)
There were 52 orders placed in the 30-day window (Aug 3 – Sep 2, 2026)! Would you like to break this down further, such as by day, status, or category?
- Generated query for input 2 · not part of the answer
SELECT COUNT(*) AS order_count FROM orders WHERE placed_at >= NOW() - INTERVAL '30 days'; - Final response
order_count 162
| ✓ | Expected: The refreshed result matches the new answer and keeps the same relative period.Found: The re-runs updated from 52 to 55 and from 162 to 164; the relative query still used the same 30-day window. |
It passes because the saved report was rerun after the data changed and returned updated counts instead of staying fixed. The fixed-date save changed from 52 to 55, and the relative save changed from 162 to 164 while keeping the same 30-day SQL.
Editable rerun. The saved report opens as editable SQL with a Run button, so it can be rerun instead of only viewed.
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 test case's result says which one 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 test case's result 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 report is run again after the data has changed → | |
| 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.