Timeline for Deleting Big Object Workaround Without Using Database.deleteImmediate
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2020 at 12:22 | comment | added | Patlatus | Ok, cool. So Salesforce has fixed internally something. | |
| Apr 7, 2020 at 1:15 | comment | added | ddeve | It looks like the solution is that even though the Known Issue is still open, the original method, outlined by Salesforce and put here using Database.deleteImmediate now works again. | |
| Apr 7, 2020 at 1:13 | vote | accept | ddeve | ||
| Mar 30, 2020 at 19:45 | comment | added | kvor | How CPU time limit will happen will happen? Limits will reset after each execution of execute(). One possible limit to reach is the 250k batch apex execution if you want to delete couple hundred thousand records (if scope == 1). | |
| Mar 30, 2020 at 17:38 | comment | added | Patlatus | I think CPU time limit might be exhausted first. However, the task here is to provide a way to delete big object records | |
| Mar 30, 2020 at 17:05 | comment | added | kvor |
Using Database.executeBatch(new DeleteBatch('select Son__c, Daughter__c from Big_Mommy__b'), 1); in a big object, could lead to Asynchronous Apex method execution limit (250k per 24h).
|
|
| Mar 29, 2020 at 19:04 | history | answered | Patlatus | CC BY-SA 4.0 |