Feature Request: some way to reap orphaned Query Locators

[alytle]

Currently there is no ability to request a session 'logout' from Salesforce.

Periodically I run into issues with the hard limit on Query Locators in Salesforce (https://help.salesforce.com/apex/HTViewSolution?id=000004410&language=en_US). When I reach the hard cap, I receive the following from Salesforce:

'INVALID_QUERY_LOCATOR' 'INVALID_QUERY_LOCATOR: invalid query locator'

The only work around right now is to just wait for the session timeout to complete, which seems to reset the available query locators.

I request we consider adding a logout command. If there is a valid way to 'close' query locators in Salesforce, without closing the session itself, that would also solve the problem.

[ellieayla]

My reading of the documentation suggests that ending the session won't reap orphaned query locators, and that they will still be subject to the 15 minute delay.

It would still be worthwhile to implement session logout, though. #18

[hynekcer]

Orphaned Query Locators is not a so big problem that it should be solved by pyforce, and not at all solved this way.

Core of problem: If the user did run a big query that is being consumed slowly by chunks in a loop and the same user executes more than 9 big queries that will not have been consumed before the main query data are consumed, then the oldest from 10 available cursors is deleted and INVALID_QUERY_LOCATOR is raised if any access to cursor is tried more.

The solution is neither to logout or to wait 15 minutes or a similar way, because the purpose is to let survive the important Query Locator enough not to kill them all. The best solution is to consume all important results immediately and to save (cache) them in a variable or in a temporary file if it is really big.

(Salesforce has more sets of independent cursors, e.g. 10 cursors for metadata. I'm not sure if 10 cursors in API are common cursors with SFDC web or not. Then a separate user account only for SOAP API could also help, if the origin of other query locators is out of your control.)