Querying, versioning, and dynamic deployment of database objects

• US 7,421,458 B1
• Filed: 10/15/2004
• Issued: 09/02/2008
• Est. Priority Date: 10/16/2003
• Status: Expired due to Fees

• Current Assignee: Informatica LLC (Informatica, Inc. (California))
• Original Assignee: Informatica Corporation
• Inventors: Wang, Rachel, Taylor, Jeff, Zheng, Li
• Primary Examiner(s): Wong; Leslie
• Application Number:
  US10/966,046
• Time in Patent Office: 1,418 Days
• Field of Search: 707/3, 707/101, 707/104.1, 707/203, 717/170, 717/174, 717/177
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

In various embodiments, the present invention provides methods and systems for creating version-stamps of database objects and for tracking, querying, retrieving, and deploying such versioned database objects in enterprise databases, data marts, or data warehouses. The database objects may be interrelated and may reference one another according to their accurate versions.

Claims

1. A method of versioning objects in a database, the objects comprising a complex object including a reference to a version number of a non-reusable object, the non-reusable object being used by only the complex object, the method comprising:

checking out the complex object, without automatically checking out the non-reusable object;

receiving a modification to the complex object, where the non-reusable object is not modified;

checking in the complex object;

incrementing a version number of the complex object, while maintaining a reference to the version of the non-reusable object;

receiving a query;

responsive to the query not including an object state criterion, returning only current versions of all objects satisfying the query; and

responsive to the query including an object state criterion, returning all versions of all objects satisfying the query.

2. The method of claim 1, further comprising:

determining at least one application that uses at least one of the complex object or the non-reusable object; and

sending a notification of the incremented version number of the used object to the at least one application to update a cached instance of the object.

3. A method of versioning objects in a database, the objects comprising a complex object including a reference to a version number of a non-reusable object, the non-reusable object being used by only the complex object, the method comprising:

checking out the complex object, without automatically checking out the non-reusable object;

receiving a modification to the complex object;

responsive to an attempted modification of the non-reusable object, checking out the non-reusable object;

checking in the complex object;

checking in the non-reusable object;

incrementing a version number of the complex object;

incrementing the version number of the non-reusable object;

updating the reference of the complex object to the incremented version number of the non-reusable object;

receiving a query;

responsive to the query not including an object state criterion returning only current versions of all objects satisfying the query; and

responsive to the query including an object state criterion returning all versions of all objects satisfying the query.

4. The method of claim 3, further comprising:

determining at least one application that uses at least one of the complex object or the non-reusable object; and

sending a notification of the incremented version number of the used object to the at least one application to update a cached instance of the object.

5. A method of fetching a version of a second object, wherein a second object is referred to by a version of a first object and it is either reusable or non-reusable, each version of the second object includes a check in time and the version of the first object including a check out time and a version number of a version of the second object, the method comprising:

responsive to the second object being non-reusable, fetching the version of the second object corresponding to the version number included in the first object, wherein the non-reusable second object is used by only the first object; and

responsive to the second object being reusable;

responsive to the version of the first object being the latest version of the first object, fetching a latest version of the second object;

responsive to the version of the first object not being the latest version of the first object, fetching the version of the second object with the most recent check in time that is prior to the first object'"'"'s check out time.