Timeline for Max aggrigate query has huge cost against # query rows returned limit
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2017 at 19:46 | vote | accept | Hans Donkersloot | ||
| Dec 20, 2017 at 19:46 | answer | added | sfdcfox♦ | timeline score: 1 | |
| Dec 20, 2017 at 19:35 | comment | added | Hans Donkersloot | Okay, Dokay, thanks for helping me think through that, if you want to put that as an answer, i'll mark it as correct | |
| Dec 20, 2017 at 19:34 | comment | added | sfdcfox♦ | Yes, formula fields result in a full table scan. You'll need to do your work asynchronously or figure a way to make it an indexed value (copy to a new field)? | |
| Dec 20, 2017 at 19:31 | comment | added | Hans Donkersloot | It's actually a formula field, I guess that since salesforce has to go through and evaluate the formula for each row it counts each one against me? | |
| Dec 20, 2017 at 19:29 | comment | added | sfdcfox♦ | The ORDER BY LIMIT 1 should only count as one row; is the field an indexed field? | |
| Dec 20, 2017 at 19:25 | history | asked | Hans Donkersloot | CC BY-SA 3.0 |