Automatic reconciliation of bindable objects

• US 7,080,088 B1
• Filed: 01/29/2003
• Issued: 07/18/2006
• Est. Priority Date: 01/30/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lau, Kwok Hung
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US10/354,429
• Time in Patent Office: 1,266 Days
• Field of Search: 707/2, 707/3, 707/4, 707/5, 707/6, 707/10, 707/101, 707/102, 705/1, 709/223, 715/503, 715/704, 715/764, 717/113, 717/125, 717/103
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Described herein is a reconciliation mechanism that facilitates reconciliation of deployment environments and dataflow descriptions. A dataflow description describes a dataflow, from which a code implementation can be generated for execution on one or more database systems, referred to as a deployment environment. To generate an implementation for a deployment environment, the elements of a dataflow description are bounded to the elements of a deployment environment. The elements of a deployment environment may change, which in turn may require changes to elements of a dataflow description that are bounded to the changed elements of the deployment environment. The reconciliation mechanism may be used to ascertain the differences between the dataflow description and the deployment environment and facilitate propagation of differences to either. The reconciliation mechanism may also be applied in other contexts, and in fact may be used to establish a binding between any sets of bindable objects.

Claims

1. A method used for reconciling a definition of a first set of entities to a definition of a second set of entities, comprising the steps:

generating a first set of objects that;

contains information derived from first metadata that defines said first set of entities, and

conforms to a common format;

generating a second set of objects that;

contains information derived from second metadata that defines said second set of entities, and

conforms to said common format;

determining differences between how first metadata defines said first set of entities and how second metadata defines said second set of entities;

wherein the step of determining differences is based on examining said first set of objects and said second set of objects;

generating a plan that specifies one or more actions for modifying said second metadata to reconcile the definition of said second set of entities with the definition of said first set of entities; and

executing the plan, wherein execution of the plan causes modification of said second metadata.

2. The method of claim 1, wherein:

the second metadata includes one or more objects that conform to a particular format; and

the step of generating a first set of objects includes generating a set of objects that conform to said particular format.

3. The method of claim 1, wherein said first set of entities include database entities.

4. The method of claim 1, wherein said second set of entities includes database entities.

5. The method of claim 1, wherein said first set of entities includes entities defined by a dataflow description.

6. The method of claim 1, wherein said second set of entities includes entities defined by a dataflow description.

7. The method of claim 1, the steps further including determining a second subset of said second set of entities that match a first subset of said first set of entities based on one or more matching criteria.

8. The method of claim 7, wherein:

for a first entity in said first subset matched to a second entity in said second subset, determining one or more differences between the definition of the first entity and the definition of the second entity; and

the step of generating an execution plan includes generating an action for modifying the definition of said second entity.

9. The method of claim 7, wherein the step of generating an execution plan includes generating, for a first entity in said first set of entities that is not matched to a second entity in said second subset, an action for modifying said second metadata to define a new entity reflecting the definition of said first entity.

10. The method of claim 9, wherein the step of generating an execution plan includes generating, for a second entity in said second set of entities not matched to a first entity in said first subset, no action item for modifying said second metadata to delete said second entity from said second set of entities, thereby merging the first set of entities and the second set of entities.

11. The method of claim 7, wherein the step of generating an execution plan includes generating, for a second entity in said second set of entities not matched to a first entity in said first subset, an action item for modifying said second metadata to delete said second entity from said second set of entities.

12. The method of claim 1, wherein:

the steps further include;

presenting the plan in a user interface to a user;

receiving user input from the user specifying changes to the plan; and

the step of generating the execution plan includes generating an execution plan that reflects said changes to the plan.

13. The method of claim 1, further including the step of:

determining a correlation between first members of said first set and second members of said second set; and

wherein the step of determining differences is based on said correlation.

14. The method of claim 13, wherein:

before executing the step of determining differences, binding data correlates at least some of said first members to said second members; and

the step of determining a correlation is based on said binding data.

15. The method of claim 13, further including:

for each first member of said first set that correlates to a second member of said second set, determining property differences between said first member and said second member.

16. The method of claim 13, wherein:

said correlation does not correlate a first member of said first set to a second member of said second set;

the step of determining differences includes determining that said second set does not include a member that correlates to said first member; and

the step of generating a plan includes generating a plan that specifies an action for adding a new member to said second set of entities that correlates to said first member.

17. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 1.

18. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 2.

19. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 3.

20. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 4.

21. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 5.

22. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 6.

23. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 7.

24. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 8.

25. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 9.

26. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 10.

27. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 11.

28. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 12.

29. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 13.

30. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 14.

31. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 15.

32. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 16.