Can I correct iDBQuery when it misreads a term or picks the wrong field?

No tool understands your business perfectly on day one, so iDBQuery is built to be teachable rather than fixed.

• Correct in the moment. If it uses `gross_amount` when you meant net, or the wrong date column, just say so — "use net revenue", "count only completed orders" — and it re-runs with your correction.
• Make it stick. Record the right interpretation in the business glossary or semantic layer: define what "revenue" means, which column is authoritative, what a synonym maps to. iDBQuery then honours that everywhere, for everyone.
• Provenance-aware. Your definitions merge with what iDBQuery learned from the schema, so corrections refine its understanding rather than resetting it.

Because every answer shows its SQL and cites source rows, spotting a misinterpretation is easy — you can see exactly which column or filter it used. Correcting it once then benefits the whole team, since shared definitions apply across conversations. This feedback loop is how iDBQuery converges on your organisation's real meaning of terms over time, turning early corrections into consistent, trustworthy answers that don't need re-explaining.