Method and system for accessing relational databases using objects

• US 5,907,846 A
• Filed: 06/07/1996
• Issued: 05/25/1999
• Est. Priority Date: 06/07/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Berner, Andrew J., Rosenthal, Kathryn A.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/657,580
• Time in Patent Office: 1,082 Days
• Field of Search: 395/612, 395/614, 395/604, 395/605, 395/606, 707/101, 707/103, 707/4, 707/5, 707/6, 707/104
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

An object oriented system for accessing an external relational database from within the object oriented system. The system creates an object and fills it with data values retrieved from the database. References from the object to other objects include pointers to preexisting objects or pointers to placeholder objects. Later retrieves fill in the placeholder objects, eliminating the need to reset the pointers. Caching, utilizing static data and static functions, is performed by each class of objects. Sub-objects are used to create different logical views of data from the database, and query access to the database is provided by a query engine which builds query language statements on demand.

Claims

1. A computer implemented method of accessing data contained in a relational database from within an object oriented environment, the method comprising the steps of:

(a) storing a data set within the relational database;

(b) receiving, within the object oriented environment, a request for data from the relational database;

(c) creating a first object within the object oriented environment, the first object containing at least one reference to a second object, the second object comprising a placeholder object, such that memory space accessible by said object oriented environment is allocated for said first object;

(d) retrieving data from the data set, wherein the data retrieved comprises data for the first object, but wherein data for the second object is not retrieved;

(e) storing the data retrieved in step (d) into the first object;

(f) returning the first object as a response to the request message;

(g) allocating memory space for said placeholder object; and

(h) setting at least one reference between said first object and said placeholder object.

2. The computer implemented method of claim 1 wherein the second object comprises a sub-object contained within the first object.

3. The computer implemented method of claim 1 wherein the second object comprises an associated object not contained within the first object.

4. The computer implemented method of claim 1 wherein step (c) further comprises creating the second object.

5. The computer implemented method of claim 4 wherein creating the second object comprises allocating memory for the second object.

6. The computer implemented method of claim 1, wherein step (b) further comprises the steps of:

(b1) determining whether the requested data is stored as an object on a cache within the object oriented environment;

(b2) when the data is stored on the cache, returning the object on the cache as a response to the request message, and not performing steps (c) through (f); and

(b3) when the requested data is not stored as an object on the cache, performing steps (c) through (f), and then placing the first object on the cache storage.

7. The computer implemented method of claim 6 wherein the first object, once created, maintains independent cache status information used by step (b1) to determine whether the requested data is available as an object on the cache.

8. The computer implemented method of claim 7 wherein the cache is implemented through static functions and static data within the first object.

9. The computer implemented method of claim 6 wherein the first object maintains independent persistence status information used by step (b1) to determine whether the requested data is available as an object on the cache.

10. The computer implemented method of claim 6 wherein the cache comprises a separate cache within each class contained within the object oriented environment.

11. The computer implemented method of claim 1 wherein the second object comprises a logical view of the first object.

12. The computer implemented method of claim 1 wherein step (d) comprises the steps of:

(d1) generating at least one query language command from mapping information stored within a retriever object;

(d2) sending the query language command to the relational database; and

(d3) receiving a result of the query language command from the relational database as the retrieved data.

13. A retriever object within an object oriented environment, the retriever object for accessing data contained in a database from within the object oriented environment, said database being arranged in tables and columns, wherein the retriever object comprises:

means for receiving a request for data from the relational database;

means for creating a first object within the object oriented environment, the first object containing at least one reference to a second object within the object oriented environment;

means for generating a query command for retrieving data from the database, wherein the data retrieved comprises data for the first object, the query command being in the query language of the relational database, and wherein said means for generating provides said query command with mapping data, said mapping data comprising table and column identifiers, and is responsive to the request;

means for storing the data retrieved into the first object; and

means for returning the first object as a response to the request message;

wherein said retriever object inherits said mapping data from a generic view retriever class.

14. The retriever object of claim 13 wherein the second object comprises a sub-object contained within the first object.

15. The retriever object of claim 13 wherein the second object comprises an associated object not contained within the first object.

16. The retriever object of claim 13, wherein said first object is a logical view of the requested data.

17. The retriever object of claim 13, wherein the means for retrieving data from the database further comprises:

means for determining whether the requested data is stored as an object on a cache within the object oriented environment;

means for returning the object on the cache as a response to the request message, when the requested data is stored on the cache; and

means for storing data retrieved from the database on the cache.

18. The retreiver object of claim 17 wherein the cache comprises a separate cache within each class contained within the object oriented environment.

19. The retriever object of claim 13 wherein said requested data is data from a number of objects and wherein said first object is a logical view providing said data.

20. A computer implemented method of accessing data contained in a relational database from within an object oriented environment, comprising the steps of:

(a) storing a data set within the relational database;

(b) receiving, within the object oriented environment, a request for data from the relational database;

(c) creating an object within the object oriented environment;

(d) retrieving data from the data set, wherein the data retrieved comprises data for the object;

(e) storing the data retrieved in step (d) into the object on a cache such that said object has a status property for indicating whether an object is available on the cache and wherein said cache status may indicate an object that has been retrieved but not put on the cache; and

,

(f) returning the first object as a response to the request message.

21. A computer implemented method of accessing data contained in a relational database from within an object oriented environment, the method comprising the steps of:

(a) storing a data set within the relational database;

(b) receiving, within the object oriented environment, a request for data from the relational database;

(c) creating an object within the object oriented environment;

(d) retrieving data from the data set, wherein the data retrieved comprises data for the object;

(e) storing the data retrieved in step (d) into the object;

(f) returning the first object as a response to the request message;

(g) providing said object with a status for determining whether the object stored in the cache is consistent with the data stored in the data storage area, wherein the status comprises a dirty state, the dirty state indicating that an object has been modified and is not consistent with the data stored in the data storage area.