Can iDBQuery query a database view?

A database view is a saved query that presents data as if it were a table. iDBQuery treats views exactly like tables: it introspects them, understands their columns through the semantic layer, and lets you ask questions in plain language.

Views are especially useful with iDBQuery because they let you shape the data on your terms:

• Expose only what's needed — build a view that selects specific columns, so sensitive fields are simply never presented to iDBQuery.
• Pre-join and clean — encode the correct joins and filters in the view, and everyone querying through iDBQuery inherits that business logic.
• Rename for clarity — alias cryptic columns to friendly names in the view, giving the semantic layer an even easier time.

Because iDBQuery queries in place, it runs against the live view every time, so answers reflect current data — and each figure is still cited back to the underlying rows the view exposes.

Example: a data team creates a 'customer_health' view that joins subscriptions, usage, and support tickets with the right logic. They point iDBQuery at that single view, and customer-success managers ask 'which accounts look at risk this month?' getting consistent, cited answers grounded in the team's official definition. If your data changes shape, you update the view once and every iDBQuery answer stays correct.