Does iDBQuery remember the context of my conversation?
Yes — within a conversation iDBQuery remembers what you've asked and the answers so far, so follow-ups can reference "that", "those customers", or "the same period" and it knows what you mean. Starting a new conversation gives a clean slate, keeping unrelated analyses from bleeding into each other.
Conversation memory is what turns a question-and-answer tool into something that supports a real train of thought.
- Carries the thread. iDBQuery tracks the entities, filters, and time frames established earlier in a conversation, so "add last year for comparison" or "exclude those" resolves against what you were just discussing.
- Scoped per conversation. Context is bounded to the current thread. Begin a new conversation and iDBQuery isn't confused by an earlier, unrelated line of questions.
- Grounded in your data, not assumptions. Memory shapes how it interprets your words, but every answer is still produced by a fresh query against the actual data and cited to source rows — it doesn't recite a remembered number back at you.
That last point matters: the context helps iDBQuery understand intent, while the numbers always come from live SQL, so the conversation stays accurate as data changes. Persistent definitions you want to reuse across all conversations — metric definitions, synonyms, fiscal calendar — live in the semantic layer and business glossary rather than in a single chat, so they apply everywhere, not just in one thread.
Updated 2026-06-22