Timeline for Is is safer (limitwise) to call Database.getQueryLocator() with SOQL String than Static SOQL?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 12, 2013 at 19:11 | vote | accept | Robert Sösemann | ||
Aug 12, 2013 at 15:45 | answer | added | sfdcfox♦ | timeline score: 7 | |
Aug 12, 2013 at 14:45 | answer | added | Jeremy Nottingham | timeline score: 2 | |
Aug 12, 2013 at 11:53 | comment | added | Robert Sösemann | This blog post (raydehler.com/cloud/clod/…) states "...that if [select id from account] returns more than the max number of rows (currently 10,000), that this will NOT throw a Governor Limit Exception." | |
Aug 12, 2013 at 9:12 | comment | added | user254875486 | I agree, the documentation doesn't really makes sense to me as well. Usually in cases like this I tend to use the least ambiguous option :-) | |
Aug 12, 2013 at 9:11 | comment | added | Robert Sösemann | Exactely that part of the docs confused me. sObject[] listOfQueries absolutely makes no sense. Any SObject array never is a List Of Queries. | |
Aug 12, 2013 at 8:59 | comment | added | user254875486 |
As far as I understand from the documentation, calling the function GetQueryLocator() officially supports two types of parameters: a String (which has the name "query") and an sObject[] (which has the name "listOfQueries"). In my opinion this indicates that you should pass a String, rather than a static SOQL query.
|
|
Aug 12, 2013 at 8:55 | comment | added | Robert Sösemann | Would be great if someone could provide a official reference to support this. | |
Aug 12, 2013 at 8:51 | comment | added | user254875486 | I've done some tests with both of the options and I think they are exactly the same. | |
Aug 12, 2013 at 7:55 | history | asked | Robert Sösemann | CC BY-SA 3.0 |