METHODS AND SYSTEMS FOR BULK ROW SAVE LOGIC IN AN OBJECT RELATIONAL MAPPING LAYER AND APPLICATION FRAMEWORK

• US 20080086447A1
• 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, Hansma, Scott, Tamm, Steven
• Granted Patent: US 8,682,863 B2
• Time in Patent Office: Days
• US Class Current: 707/2
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/284 Relational databases

Abstract

In accordance with embodiments, there are provided mechanisms and methods for saving multiple rows together through an object relational mapping layer to a database. These mechanisms and methods for saving multiple rows together can enable embodiments to detect faults in the save operation(s) and recover. The ability of embodiments to detect faults in the save operation(s) and recover can enable embodiments to provide a robust forgiving published API that saves a set of rows together whenever possible.

Claims

1. A method for saving multiple rows together through an object relational mapping layer to a database, the method comprising:

receiving, at an API in a known start state, a set of rows to save together;

saving the set of rows together until each row in the set of rows has been saved;

forming a new set of rows from the set of rows by removing rows associated with faulting during saving; and

repeatedly saving and forming using the new set of rows until a set of rows that can be saved from the known start state without fault is determined.

2. The method of claim 1, wherein receiving, at an API in a known start state, a set of rows to save together includes:

receiving information to save to a set of rows in a Simple Object Access Protocol (SOAP) transaction.

3. The method of claim 1, wherein saving the set of rows together until each row in the set of rows has been saved includes:

recording fault information for any row associated with a save operation that faults.

4. The method of claim 1, wherein forming a new set of rows from the set of rows by removing rows associated with faulting during saving includes:

removing rows corresponding to faults from the set of rows to save together to form the new set of rows to save together.

5. The method of claim 1, wherein repeatedly saving and forming using the new set of rows until a set of rows that can be saved from the known start state without fault is determined includes:

rolling back saving the set of rows to the known start state.

6. The method of claim 5, wherein rolling back saving the set of rows to the known start state includes:

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

7. The method of claim 1, further comprising:

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

8. The method of claim 7, thereby enabling:

ensuring that no side effects have occurred from executing code on behalf of any rows failing to be saved.

9. A machine-readable medium carrying one or more sequences of instructions for saving multiple rows together through an object relational mapping layer to a database, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving, at an API in a known start state, a set of rows to save together;

saving the set of rows together until each row in the set of rows has been saved;

forming a new set of rows from the set of rows by removing rows associated with faulting during saving; and

repeatedly saving and forming using the new set of rows until a set of rows that can be saved from the known start state without fault is determined.

10. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of receiving, at an API in a known start state, a set of rows to save together include instructions for carrying out the step of:

receiving information to save to a set of rows in a Simple Object Access Protocol (SOAP) transaction.

11. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of saving the set of rows together until each row in the set of rows has been saved include instructions for carrying out the step of:

recording fault information for any row associated with a save operation that faults.

12. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of forming a new set of rows from the set of rows by removing rows associated with faulting during saving include instructions for carrying out the step of:

removing rows corresponding to faults from the set of rows to save together to form the new set of rows to save together.

13. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of repeatedly saving and forming using the new set of rows until a set of rows that can be saved from the known start state without fault is determined include instructions for carrying out the step of:

rolling back saving the set of rows to the known start state.

14. The machine-readable medium as recited in claim 13, wherein the instructions for rolling back saving the set of rows to the known start state 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.

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

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

16. The machine-readable medium as recited in claim 15, wherein the instructions for committing the set of rows when no fault(s) have occurred include instructions for carrying out the step of:

ensuring that no side effects have occurred from executing code on behalf of any rows failing to be saved.

17. An apparatus for saving multiple rows together through an object relational mapping layer to a database, 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;

receiving, at an API in a known start state, a set of rows to save together;

saving the set of rows together until each row in the set of rows has been saved;

forming a new set of rows from the set of rows by removing rows associated with faulting during saving; and

repeatedly saving and forming using the new set of rows until a set of rows that can be saved from the known start state without fault is determined.

18. A method for transmitting code for saving multiple rows together through an object relational mapping layer to a database on a transmission medium, the method comprising:

transmitting code to receive, at an API in a known start state, a set of rows to save together;

transmitting code to save the set of rows together until each row in the set of rows has been saved;

transmitting code to form a new set of rows from the set of rows by removing rows associated with faulting during saving; and

transmitting code to repeatedly save and form using the new set of rows until a set of rows that can be saved from the known start state without fault is determined.

19. A method for saving multiple rows together through an object relational mapping layer to a database, the method comprising:

(A) receiving, at an API in a known start state, a set of rows to save together;

(B) attempting to save the set of rows together, while recording fault information for any save operation that faults, until each row in the set of rows has been attempted at least once; and

(c) committing the save of the entire set of rows if no fault(s) have occurred;

otherwise

(i) rolling back the save of the entire set of rows to the known start state;

(ii) removing rows corresponding to faults from the set of rows to save together to form a subset of rows to save together; and

(iii) repeating steps (B)-(C) using the subset of rows as a new set of rows to save together until a subset of rows that can be saved and committed without fault is found.