AskYourDatabase in AI Database Agents

AskYourDatabase's reported totals matched what actually happened in this run. Person 1 showed 3 conversations and Person 2 showed 2, and both included unanswered questions; the five-message list in the capture matches the five questions that were run.

AskYourDatabase answered this case in a plain sentence. The chat shows "You've received 308 total orders to date." and the pane shows no chart or one-cell table. The answer matches the recorded total of 308 orders.

AskYourDatabase gave a headline figure and a breakdown in forms suited to each, so it met the scenario. It returned a revenue summary table for the total, a category table for the breakdown, and takeaways naming the driver; there was no chart.

AskYourDatabase changed the answer from a table to a chart without changing the values. The earlier reply shows a seven-category revenue table for August 2026. The charted reply prints the same seven category amounts beside the bars, and the code shown in the chat fetches saved data instead of running new SQL.

AskYourDatabase handled a customer correction in this conversation. After the July 2026 question returned 23 orders, the follow-up “Sorry, I meant June 2026.” triggered fresh June-only SQL and a June answer of 10.

AskYourDatabase did not ask for clarification when a follow-up was ambiguous. The first answer created two distinct customer lists, and the second turn answered with a side-by-side comparison instead of asking which list was meant.

AskYourDatabase handles the mid-conversation change by dropping the earlier Texas filter and answering with the broader all-states breakdown. The second query has no state condition, and the 15-row table totals 308 orders and 67 cancellations; the Texas turn stays separate at 18 orders and 27.78%.

AskYourDatabase handles this narrowing case: it keeps the earlier question’s date window and adds the new Texas constraint. In the first turn, the app returned 59 orders in a 10-row preview plus a full CSV. In the follow-up, it kept the same window, returned 3 Texas orders, and those three all appear in the first turn’s 59-row CSV.

AskYourDatabase could not answer the question from the connected data. It said the schema it could see had no review or rating data, asked where that data is stored, and returned no number.

AskYourDatabase handled the company-defined term by stating the definition it used instead of giving a bare number. It named revenue as order totals, excluded cancelled orders, and offered other bases; the answer’s heading and SQL also showed a June 4–September 2 span under a 90-day label.

AskYourDatabase handled a request whose wording differed from the stored value in the tested turn. It rewrote "gift voucher" as "gift card", queried the stored value, and returned 14 matching orders instead of an empty result. The answer view shows the table and a note that two orders were later cancelled.

AskYourDatabase put the three findings into one combined chat reply, and the figures matched the earlier direct answers. The report was a formatted assistant reply, not a saved file. It reported revenue excluding cancelled orders, Home Decor as the best-selling category by units, and both order and subscription cancellation rates.