Does iDBQuery use live or cached data?

By default, iDBQuery queries your databases and warehouses live, so an answer reflects their exact state at the moment you ask; there is no overnight copy sitting in between. Query-in-place means the source is the single version of the truth.

Some source types work differently by nature: - Documents, PDFs and folders of files are read and indexed on a sync schedule you set, because they are not live query engines. You can re-sync them on demand. - REST APIs and warehouses are queried according to how you have configured the connection and any sync interval.

A worked example: ask 'how many orders today?' against a connected database and you get the current count; ask a question over a folder of scanned invoices and the answer reflects the last index run, which you can refresh anytime.

The differentiator is transparency about freshness. Because every figure is cited to its source, and iDBQuery distinguishes live sources from indexed ones, you always know whether a number is live or as-of the last sync. That matters for reporting: you can trust that a live database figure is current, and you control the refresh cadence for document sources. There is no hidden cache silently serving stale numbers; the source and its recency are always visible behind the answer.