How does iDBQuery handle an ambiguous question?

iDBQuery does not guess silently when a question is unclear; it makes its interpretation visible so you can correct it in one step: - If the question is genuinely ambiguous, it asks a clarifying question, for example which 'revenue' you mean (booked, recognised, collected) or which date range. - If it can reasonably proceed, it states the assumption it made and shows the SQL it wrote, so the interpretation is right there to check.

A worked example: you ask 'show me top customers.' iDBQuery might answer by total spend this year while noting 'ranked by total revenue in 2026, say the word if you meant order count or a different period,' and you refine with a one-line follow-up.

The differentiator is that ambiguity surfaces instead of hiding. A plain text-to-SQL tool often returns a confident but wrong number because it quietly picked a column; iDBQuery grounds the query in your real schema and semantic layer, shows its work, and cites the result, so a misread is obvious and cheap to fix. Because it is conversational, correcting an assumption is just the next message, 'no, use recognised revenue and last quarter,' rather than rewriting a query. The result is fewer confidently-wrong answers and more that you can trust.