Can I review and edit iDBQuery's SQL before or after it runs?

iDBQuery writes the SQL so you don't have to, but it doesn't lock you out of it.

• Review first. Because the generated query is visible, an analyst can read it before trusting the result and confirm it matches intent.
• Refine in plain language. Most users never touch SQL — they just say "exclude internal accounts" or "only completed orders" and iDBQuery adjusts the query. This is the fastest path for non-technical people.
• Edit the SQL directly. Where a data professional wants precise control, they can take the generated SQL as a starting point and modify it — a huge time-saver over writing complex joins from scratch.

This two-way flexibility is why iDBQuery suits mixed teams: the CFO asks in words, the analyst fine-tunes the query, and both land on the same trustworthy, cited answer. And because every result carries row-level citations and the query stays on screen, any edit — whether phrased in English or written in SQL — remains transparent and checkable rather than a hidden change to how the number was produced.