TRACKING CONSTRAINTS AND DEPENDENCIES ACROSS MAPPING LAYERS

• US 20100082646A1
• Filed: 09/26/2008
• Published: 04/01/2010
• Est. Priority Date: 09/26/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Poliakova, Nadejda, Meek, Colin
• Application Number:
  US12/239,104
• Publication Number:
  US 20100082646A1
• Time in Patent Office: Days
• US Class Current: 707/752
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

Techniques for object relational mapping (ORM) are provided. A dependency graph generator receives a combination of object level custom commands and store level dynamic commands. Each store level dynamic command is generated from at least one object level dynamic command. An identifier is assigned to each entity present in the object level custom commands and the object level dynamic commands. A store level dynamic command includes any identifiers assigned in the corresponding object level dynamic command(s). The dependency graph generator is configured to generate a dependency graph that includes nodes and at least one edge coupled between a corresponding pair of nodes. Each node is associated with a corresponding store level dynamic command or an object level custom command. An edge is configured according to an identifier associated with the corresponding pair of nodes and a dependency between commands associated with the corresponding pair of nodes.

Claims

1. A method for object relational mapping, comprising:

generating at least one object level custom command for at least one object modification in an object graph determined to be configured to be processed at an application level;

generating at least one object level dynamic command for at least one object modification in the object graph determined to be configured to be processed at a store level, the at least one object level dynamic command and the at least one object level custom command forming a plurality of object level commands;

assigning an identifier to each entity present in the object level commands;

assigning a pair of the identifiers to each relationship present in the object level commands, the pair of identifiers assigned to a first relationship being first and second identifiers respectively assigned to first and second entities included in the first relationship;

converting the at least one object level dynamic command to at least one store level dynamic command;

generating a dependency graph that includes a plurality of nodes and an edge coupled between a pair of nodes of the plurality of nodes, each node being associated with a corresponding store level dynamic command or an object level custom command;

configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes; and

performing a topological sort of the dependency graph to determine an execution order of the store level dynamic commands and the object level custom commands.

2. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

configuring the edge according to a foreign key dependency between the commands associated with the pair of nodes.

3. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a first command to delete a primary key or to insert a foreign key;

determining a second node associated with a second command to delete a foreign key or to insert a primary key; and

coupling the edge between the first and second nodes to have a direction from the second node to the first node.

4. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

configuring the edge according to a common value dependency between the commands associated with the pair of nodes.

5. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a common value to be generated and an assigned identifier associated with the common value;

determining a second node that requires the generated common value to be received and includes the assigned identifier; and

coupling the edge between the first and second nodes to have a direction from the first node to the second node.

6. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

configuring the edge according to a model ordering dependency between the commands associated with the pair of nodes.

7. The method of claim 1, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a first command to insert an entity or to delete a relationship and that includes an assigned identifier;

determining a second node associated with a second command to insert a relationship or to delete the entity and that includes the assigned identifier; and

coupling the edge between the first and second nodes to have a direction from the first node to the second node.

8. An object relational mapping (ORM) system, comprising:

a dependency graph generator that receives at least one object level custom command and at least one store level dynamic command, the at least one store level dynamic command being generated from at least one object level dynamic command, an identifier being assigned to each entity present in the at least one object level custom command and to each entity present in the at least one object level dynamic command, the at least one store level dynamic command including any identifiers assigned in the at least one object level dynamic command;

the dependency graph generator being configured to generate a dependency graph that includes a plurality of nodes and an edge coupled between a pair of nodes of the plurality of nodes, each node being associated with a corresponding store level dynamic command or an object level custom command; and

the dependency graph generator being configured to configure the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes.

9. The ORM system of claim 8, wherein the dependency is a foreign key dependency, a common value dependency, or a model ordering dependency.

10. The ORM system of claim 8, wherein the dependency graph generator includes a foreign key dependency edge determiner, the foreign key dependency edge determiner being configured to determine a first node associated with a first command to delete a primary key or to insert a foreign key, to determine a second node associated with a second command to delete a foreign key or to insert a primary key, and to couple the edge between the first and second nodes to have a direction from the second node to the first node.

11. The ORM system of claim 8, wherein the dependency graph generator includes a common value dependency edge determiner, the common value dependency edge determiner being configured to determine a first node associated with a common value to be generated and an assigned identifier associated with the common value, to determine a second node that requires the generated common value to be received and includes the assigned identifier, and to couple the edge between the first and second nodes to have a direction from the first node to the second node.

12. The ORM system of claim 8, wherein the dependency graph generator includes a model ordering dependency edge determiner, the model ordering dependency edge determiner being configured to determining a first node associated with a first command to insert an entity or to delete a relationship and that includes an assigned identifier, to determine a second node associated with a second command to insert a relationship or to delete the entity and that includes the assigned identifier, and to couple the edge between the first and second nodes to have a direction from the first node to the second node.

13. The ORM system of claim 8, further comprising:

a topological sorter configured to perform a topological sort of the dependency graph to determine an execution order of the store level dynamic commands and the object level custom commands.

14. A method for generating a dependency graph, comprising:

receiving at least one object level custom command and at least one store level dynamic command, the at least one store level dynamic command being generated from at least one object level dynamic command, an identifier being assigned to each entity present in the at least one object level custom command and to each entity present in the at least one object level dynamic command, the at least one store level dynamic command including any identifiers assigned in the at least one object level dynamic command;

generating a dependency graph that includes a plurality of nodes and an edge coupled between a pair of nodes of the plurality of nodes, each node being associated with a corresponding store level dynamic command or an object level custom command; and

configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes.

15. The method of claim 14, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

configuring the edge according to an assigned identifier associated with the pair of nodes and a foreign key dependency, a common value dependency, or a model ordering dependency between commands associated with the pair of nodes.

16. The method of claim 14, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a first command to delete a primary key or to insert a foreign key;

determining a second node associated with a second command to delete a foreign key or to insert a primary key; and

coupling the edge between the first and second nodes to have a direction from the second node to the first node.

17. The method of claim 14, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a common value to be generated and an assigned identifier associated with the common value;

determining a second node that requires the generated common value to be received and includes the assigned identifier; and

coupling the edge between the first and second nodes to have a direction from the first node to the second node.

18. The method of claim 14, wherein said configuring the edge according to an assigned identifier associated with the pair of nodes and a dependency between commands associated with the pair of nodes comprises:

determining a first node associated with a first command to insert an entity or to delete a relationship and that includes an assigned identifier;

determining a second node associated with a second command to insert a relationship or to delete the entity and that includes the assigned identifier; and

coupling the edge between the first and second nodes to have a direction from the first node to the second node.