A report cursor keeps its database result set open past the connection lease so rows can be pulled lazily. Reaching the end only marked it finished. On 7 October the one-row count cursors of the home cards were still open twenty minutes after the page was read, and their handles on the log tables refused a table rename.
What changed
- Released at the end Once every row, totals included, is in the report's own store, the engine cursor is closed. Close, cancel and column lookup answer without it.
- Behind a flag, then by default Shipped off on 7 October and switched on two days later; a property or a setter keeps the old behaviour for a report that needs it.
- Named honestly A method called exhausted now says what the last-row check had answered since 2022: the data is exhausted, not the cursor is on its last row.
- Answers that own a cursor close it after writing; the foreign-key advanced search was the first caller.
A dashboard of many cards held one open cursor per card until the session cache evicted it. Now it holds none.