Holding cursor open

[detule]

Currently, while paging in the main execution window, or in the table preview we hold the cursor open, and only fetch a new result set when the user asks / prompts the client to see a new page-worth-of-data.

This is fine, however in situations where the user, for example, steps away from the client for hours (days?) you end up unnecessarily holding an open session to the server, which might in turn, for example show up on various DBA alerts.

Possible solutions:

• Continue to fetch async regardless of whether the user is prompting for a new page, until such time that the result set is depleted OR the user exits the pager / preview window. Probably some contentious thread locking will be needed here.
• Some sort of a time-out?