Timeline for Governor limits : Database.getQueryLocator
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2018 at 15:39 | comment | added | sfdcfox♦ |
@WillemMulder You're still limited to 50,000 normal query rows, both inline and database query methods, but the QueryLocator you return from the start method won't count. You can use inline queries or strings with getQueryLocator (return database.getquerylocator([select...]) works just fine).
|
|
| Apr 11, 2018 at 15:05 | comment | added | Willem Mulder | @sfdcfox if we return a QueryLocator from the start() method, and the limits are bypassed, does that mean that we can do any kind of queries in the start() method and they will not count against the limit? Or is the limit bypass only valid for a QueryLocator that is constructed using a String, and all other queries count against the limits as usual? | |
| Jan 30, 2015 at 15:50 | comment | added | sfdcfox♦ | Exactly. Using a standard set controller, you can pass in a query locator, but it has to have at most 10000 rows. | |
| Jan 30, 2015 at 11:25 | comment | added | user9959 | So, I simply ignored that we can use getQueryLocator outside a batch start() ! | |
| Jan 30, 2015 at 11:22 | comment | added | user9959 | Thanks.. I was forgetting that in a start() method, using getQueryLocator the limits are not enforced. (it was a purely theorical question, de facto I knew and I experienced those limits are not enforced.) | |
| Jan 30, 2015 at 11:19 | vote | accept | CommunityBot | ||
| Jan 30, 2015 at 11:19 | history | answered | Dominic | CC BY-SA 3.0 |