CUSTOMIZABLE METADATA MERGING FRAMEWORK

• US 20090083340A1
• Filed: 11/25/2008
• Published: 03/26/2009
• Est. Priority Date: 12/29/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Baskaran, Rajagopal, Singson, Jaime E.
• Granted Patent: US 8,103,641 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

One embodiment of the present invention provides a system that facilitates merging different versions of a database object. During operation, the system receives metadata associated with a first version of a database object and a second version of the database object. The system then compares metadata associated with the first version with metadata associated with the second version to create a difference report. Next, the system uses the different report to create an action plan that specifies how to merge the metadata associated with the first and second versions of the metadata object.

Claims

1. A computer implemented method to facilitate merging different versions of a database object, comprising:

receiving metadata associated with a first version of the database object and a second version of the database object;

creating a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;

creating an action plan from the difference report, wherein the action plan specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;

receiving an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and

facilitating merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan, wherein the first version and second version of the database object include other objects.

2. The method of claim 1, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.

3. The method of claim 1, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.

4. The method of claim 1, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.

5. The method of claim 1, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.

6. The method of claim 1, wherein metadata associated with first and second versions of the metadata object can define database objects, wherein database objects include tables, columns, dimensions, cube, views, materialized views, and external tables.

7. The method of claim 1, wherein the action plan can specify a number of actions including creating, updating, and deleting database objects, and their properties.

8. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method to facilitate merging different versions of a database object, the method comprising:

receiving metadata associated with a first version of the database object and a second version of the database object;

creating a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;

creating an action plan from the difference report, wherein the action plan specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;

receiving an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and

facilitating merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan, wherein the first version and second version of the database object include other objects.

9. The computer-readable storage medium of claim 8, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.

10. The computer-readable storage medium of claim 8, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.

11. The computer-readable storage medium of claim 8, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.

12. The computer-readable storage medium of claim 8, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.

13. The computer-readable storage medium of claim 8, wherein metadata associated with first and second versions of the metadata object can define database objects, wherein database objects include tables, columns, views, dimensions, and cubes.

14. The computer-readable storage medium of claim 8, wherein the action plan can specify a number of actions including creating, updating, and deleting database objects and their properties.

15. An apparatus to facilitate merging different versions of a database object, comprising:

a processor;

a memory;

a receiving mechanism configured to receive metadata associated with a first version of the database object and a second version of the database object;

a difference-report-creating mechanism configured to create a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;

an action-plan creating mechanism configured to create an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;

a receiving mechanism configured to receive an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and

a merging mechanism configured to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan.

16. The apparatus of claim 15, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.

17. The apparatus of claim 15, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.

18. The apparatus of claim 15, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.

19. The apparatus of claim 15, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.

20. The apparatus of claim 15, wherein metadata associated with first and second versions of the metadata object can define tables, columns, properties of tables, and properties of columns.

21. The apparatus of claim 15, wherein the action plan can specify a number of actions including creating, updating, and deleting tables, columns, or properties.