Two additions improve auditability and transparency for object-based queries. The platform records each query-by-example execution to a per-user history table, and the UI surfaces the cursor's hint annotation directly in the toolbar rather than requiring the operator to open the query definition to identify the active variant.
QBE query history
- Per-user log table. Every QBE object query execution writes a row with the user, object identifier, timestamp, and resolved query parameters. The table covers object-query execution only — it does not log free-form SQL.
- Queryable through standard surfaces. Administrators can audit which users ran which object queries and when, without parsing server logs.
- Non-blocking write. The history write is asynchronous relative to query result delivery; it does not add latency to the query path.
Cursor hint in toolbar
- Subtitle below the object title. When a cursor definition carries a hint string, the toolbar renders it as a secondary line below the display name, visible immediately on page load.
- Schema-driven. The hint is set in the cursor definition at the schema level; no per-deployment UI configuration is required to display it.
The toolbar hint tells the operator which query is active; the history log confirms when it ran — together they close the diagnostic gap in objects with multiple query variants without requiring access to the server log stream.