Timeline for Limiting rows returned from a query
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2018 at 21:35 | comment | added | sfdcfox♦ |
@loremIpsum1771 You have a query in a loop. What happens if you have 200 records in campaigns? Even if you don't think you'll ever have it process that many, you can't predict that someone in the future won't try to repurpose your method to do so.
|
|
| Mar 1, 2018 at 21:20 | comment | added | loremIpsum1771 |
@sfdcfox What needs to be bulkified? cmp.Mailing_ID__c will store at most one value at a time.
|
|
| Mar 1, 2018 at 17:50 | comment | added | sfdcfox♦ | Before you even think about putting this in production, do yourself a favor and bulkify. As written, you'll run into SOQL governor limits that may prevent you from performing critical data updates. | |
| Mar 1, 2018 at 17:48 | comment | added | caleb.breckon |
You need a colon. Available_Mailing__C =: cmp.Mailing_ID__c
|
|
| Mar 1, 2018 at 17:44 | answer | added | David Reed | timeline score: 4 | |
| Mar 1, 2018 at 17:40 | history | asked | loremIpsum1771 | CC BY-SA 3.0 |