Method and apparatus for extending existing database management system for new data types

• US 5,794,250 A
• Filed: 04/18/1997
• Issued: 08/11/1998
• Est. Priority Date: 10/20/1995
• Status: Expired due to Term

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: NCR Corporation (NCR Voyix Corporation)
• Inventors: Carino, Felipe Jr., Sterling, Warren M.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US08/844,476
• Time in Patent Office: 480 Days
• Field of Search: 707/100, 707/4, 707/104
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A method and apparatus for extending a relational database management system performed by a computer to manage object data stored in an object server having a processor and a data storage device. The method comprises the steps of receiving a database command including a store command and object data from a client at a federated coordinator, generating a data surrogate unique to the object data, associating the data surrogate with the object data, and storing the data surrogate and the object data in the data storage device in the object server.

Claims

1. An object-relational database management system, comprising:

a relational database management system (RDBMS);

an object server for storing object data;

a client interface, for receiving a database command from a client and for transforming the database command into a federated coordinator command; and

a federated coordinator, communicatively coupled the client interface, the RDBMS and the object server, for transforming the federated coordinator command to an object server command and a federated coordinator RDBMS command comprising a data surrogate for managing the object data;

wherein the client interface further comprises a native RDBMS interface module for managing communications between the RDBMS and the client, the native RDBMS interface communicatively coupled directly to the RDBMS.

2. The apparatus of claim 1, wherein the RDBMS stores relational database data and object-relational database data, and the client interface comprises means for preventing the client RDBMS commands from modifying the object-relational database data.

3. The apparatus of claim 1, wherein the client interface further comprises a first module for managing communications between the client and the federated coordinator and a second module for managing communications between the object server and the client.

4. The apparatus of claim 3, wherein the first module is communicatively coupled to the federated coordinator via a first communications path and the second module is communicatively coupled to the object server via a second communications path, the second communication path having a bandwidth greater than the first communications path.

5. The apparatus of claim 3, wherein the first module is communicatively coupled to the federated coordinator via a first communications path and the second module is communicatively coupled to the object server via a second communications path, wherein the second communication path more secure than the first communications path.

6. The apparatus of claim 1, wherein the federated coordinator further comprises:

means for parsing the federated coordinator command into a parse tree of object structures comprising RDBMS commands and object server commands, said parse tree comprising parse tree nodes;

means for obtaining cost parameters for the parse object structures from a global data dictionary;

means for binding the cost parameters to the parse tree nodes;

means for iterating over the parse tree object structures to evaluate parse tree options according to the cost parameters and a selection criteria; and

means for selecting the parse tree option based upon the cost parameters and selected criteria.

7. A method of extending a relational database management system (RDBMS) to respond to object-relational database commands to manage object data stored in an object server comprising a processor and a data storage device, the method comprising the steps of:

receiving a database command from a client at a client interface;

supplying the database command directly to the RDBMS when the database command is only a RDBMS command;

supplying the database command to a federated coordinator when the database command is an object-relational database command comprising a store command and object data;

generating an alphanumeric data surrogate unique to the object data;

associating the object data with the alphanumeric data surrogate;

storing the data surrogate and the object data in the data storage device in the object server; and

storing the data surrogate in the relational database.

8. The method of claim 7 further comprising the step of transmitting the data surrogate to the client.

9. The method of claim 8 further comprising the steps of:

receiving a database command comprising a retrieve command and the data surrogate from the client;

transmitting the data surrogate to the object server; and

transmitting the object data to the client.

10. The method of claim 9 further comprising the step of transmitting the object data to a second client.

11. The method of claim 10 wherein the step of transmitting the object data to a second client comprises the steps of:

transmitting the data surrogate to a second client;

receiving a database command comprising a retrieve command and the data surrogate from the second client;

transmitting the data surrogate to the object server; and

transmitting the object data associated with the data surrogate to the second client.

12. The method of claim 9, wherein the data surrogate is transmitted via a first communication path and the object data is transmitted to the client on a second communication path, the second communication path having a bandwidth greater than the first communication path.

13. The method of claim 9, wherein the object data is transmitted to the client on a first communication path and the object data is transmitted to the client on a second communication path, the second communication path more secure than the first communications path.

14. The method of claim 7, further comprising the steps of:

receiving a second database command in the client interface, the second database command to retrieve data stored in the object server;

transforming the second database command into a second federated coordinator command;

transforming the second database command into RDBMS commands and object server commands comprising a second data surrogate identifying data responsive to the second database command;

wherein the step of transforming the second database command into RDBMS commands and object server commands comprises the steps of parsing the federated coordinator command into a parse tree of object structures comprising RDBMS commands and object server commands, said parse tree comprising parse tree nodes, obtaining cost parameters for the parse object structure from a global data dictionary, binding the cost parameters to the parse tree nodes, iterating over the parse tree object structures to evaluate parse tree options according to the cost parameters and a selection criteria, and selecting the parse tree option based upon the cost parameters and selected criteria;

transmitting the data surrogate to the object server; and

transmitting the object data to the client.

15. A program storage device, readable by a computer having a processor and a data storage device, tangibly embodying one or more programs of instructions executable by the computer to perform method steps of extending a relational database management system to manage object data stored in an object server comprising a processor and a data storage device, the method comprising the steps of:

receiving a database command from a client at a client;

supplying the database command directly to the RDBMS when the database command is only a RDBMS command;

supplying the database command to a federated coordinator when the database command is an object-relational database command comprising a store command and object data;

generating an alphanumeric data surrogate unique to the object data;

associating the object data with the alphanumeric data surrogate;

storing the data surrogate and the object data in the data storage device in the object server; and

storing the data surrogate in the relational database.

16. The program storage device of claim 15 wherein the method steps further comprise the method step of transmitting the data surrogate to the client.

17. The program storage device of claim 16 wherein the method steps further comprise the method steps of:

receiving a database command comprising a retrieve command and the data surrogate from the client;

transmitting the data surrogate to the object server; and

transmitting the object data to the client.

18. The program storage device of claim 17 wherein the method steps further comprise the step of transmitting the object data to a second client.

19. The program storage device of claim 18 wherein the method step of transmitting the object data to a second client comprises the method steps of:

transmitting the data surrogate to a second client;

receiving a database command comprising a retrieve command and the data surrogate from the second client;

transmitting the data surrogate to the object server; and

transmitting the object data associated with the data surrogate to the second client.

20. The program storage device of claim 17 wherein the object data is transmitted to the second client on a communication path having a bandwidth greater than the first communication path.

21. The program storage device of claim 17, wherein the object data is transmitted to the client on a first communication path and the object data is transmitted to the client on a second communication path, the second communication path more secure than the first communications path.

22. The program storage device of claim 15, wherein the method steps further comprise the steps of:

receiving a second database command in the client interface, the second database command to retrieve data stored in the object server;

transforming the second database command into a second federated coordinator command;

transforming the second database command into RDBMS commands and object server commands comprising a second data surrogate identifying data responsive to the second database command;

wherein the step of transforming the second database command into RDBMS commands and object server commands comprises the steps of parsing the federated coordinator command into a parse tree of object structures comprising RDBMS commands and object server commands, said parse tree comprising parse tree nodes, obtaining cost parameters for the parse object structure from a global data dictionary, binding the cost parameters to the parse tree nodes, iterating over the parse tree object structures to evaluate parse tree options according to the cost parameters and a selection criteria, and selecting the parse tree option based upon the cost parameters and selected criteria;

transmitting the data surrogate to the object server; and

transmitting the object data to the client.