Can BlazeSQL consistently apply a user's standing rule across future answers?

Response to input 1
Got it! From now on, I'll always filter out cancelled orders (i.e. status != 'cancelled') in any revenue totals or order counts, unless you specifically ask me to include them.

Tip: To make this rule permanent across sessions, add it to your Knowledge Base via the Train Blaze page so I'll always remember it — even in future conversations.

Anything else you'd like to explore?

SUGGESTED NOTE SAVED BY THE TOOL (21 September 2026, 14:50):
Always exclude cancelled orders (status = 'cancelled') from all revenue and order-count calculations unless the user explicitly requests otherwise.
Table: orders
Column: status

Response to input 2
Generated query: Total Revenue This Year

SELECT
    SUM(total_amount) AS total_revenue
FROM orders
WHERE
    status != 'cancelled'
    AND EXTRACT(YEAR FROM placed_at) = 2026

Query logic:
1. Filter orders placed in 2026 and exclude cancelled orders.
2. Sum total_amount to get total revenue.

total_revenue
51,848.02

Done! Cancelled orders are excluded as requested. Would you like to break this down further — by month, category, or something else?

Response to input 3
Generated query: Order Count Last Month

SELECT
    COUNT(*) AS order_count
FROM orders
WHERE
    status != 'cancelled'
    AND EXTRACT(YEAR FROM placed_at) = 2026
    AND EXTRACT(MONTH FROM placed_at) = 8

Query logic:
1. Filter orders placed in August 2026 and exclude cancelled orders.
2. Count the remaining orders.

order_count
32

There you go — August 2026 order count, cancelled orders excluded! Want to dig deeper, like comparing it to previous months?