METHODS AND SYSTEMS FOR PROVIDING FAULT RECOVERY TO SIDE EFFECTS OCCURRING DURING DATA PROCESSING

• US 20080086514A1
• Filed: 02/23/2007
• Published: 04/10/2008
• Est. Priority Date: 10/04/2006
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Fisher, Steve, Weissman, Craig, Wong, Simon, Fell, Simon, Tamm, Steven
• Granted Patent: US 8,161,010 B2
• Time in Patent Office: Days
• US Class Current: 707/200
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence

Abstract

Embodiments may recover from faults by forming a new set of rows by removing rows associated with faulting save operations and repeating the saving and forming operations using the new set of rows until a set of rows that can be saved from the known start state without fault is determined. When the subset of successful rows is found, embodiments are able to provide assurance that no side effects (i.e., code or operations triggered by saving of a data to a particular location) have been executed on behalf of any of the failed rows (side effects from custom PL/SOQL code included) by deferring execution of triggers until an entire set of rows can be saved and committed.

Claims

1. A method for providing fault recovery to side effects occurring during data processing, the method comprising:

detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect;

rolling back each of the set of rows processed and retrying processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed to the database without fault is determined; and

processing the subset of rows to the database and executing the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault.

2. The method of claim 1, wherein detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect includes:

detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one of a pre-operation trigger, a post-operation trigger, a code snippet.

3. The method of claim 1, wherein rolling back each of the set of rows processed and retrying processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed includes:

rolling back governor limits placed upon code executing on behalf of rows that are being rolled back.

4. The method of claim 1, wherein processing the subset of rows to the database and executing the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault includes:

updating resources used and checking against governor limits.

5. The method of claim 1, further comprising:

committing the set of rows when no fault(s) have occurred.

6. A machine-readable medium carrying one or more sequences of instructions for providing fault recovery to side effects occurring during data processing, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect;

rolling back each of the set of rows processed and retrying processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed; and

processing the subset of rows to the database and executing the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault.

7. The machine-readable medium as recited in claim 6, wherein the instructions for carrying out the step of detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect include instructions for carrying out the step of:

detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one of a pre-operation trigger, a post-operation trigger, a code snippet.

8. The machine-readable medium as recited in claim 6, wherein the instructions for carrying out the step of rolling back each of the set of rows processed and retrying processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed include instructions for carrying out the step of:

rolling back governor limits placed upon code executing on behalf of rows that are being rolled back.

9. The machine-readable medium as recited in claim 6, wherein the instructions for carrying out the step of processing the subset of rows to the database and executing the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault include instructions for carrying out the step of:

updating resources used and checking against governor limits.

10. The machine-readable medium as recited in claim 6, further comprising instructions for carrying out the step of:

committing the set of rows when no fault(s) have occurred.

11. An apparatus for providing fault recovery to side effects occurring during data processing, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

detecting a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect;

rolling back each of the set of rows processed and retrying processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed; and

processing the subset of rows to the database and executing the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault.

12. A method for transmitting code for providing fault recovery to side effects occurring during data processing on a transmission medium, the method comprising:

transmitting code to detect a fault in processing a set of rows of a database, wherein at least one of the set of rows includes at least one side effect;

transmitting code to roll back each of the set of rows processed and retry processing on a subset of the set of rows in which rows associated with faults have been removed until a subset of the set of rows in which each row of the subset of rows is able to be processed; and

transmitting code to process the subset of rows to the database and execute the at least one side effect, thereby ensuring that no side effects have occurred from executing code on behalf of any rows associated with a fault.