OBJECT PROCESS GRAPH RELATIONAL DATABASE INTERFACE

• US 20060004851A1
• Filed: 05/20/2005
• Published: 01/05/2006
• Est. Priority Date: 07/02/2004
• Status: Active Grant

• Current Assignee: Graphlogic, Inc.
• Original Assignee: Graphlogic, Inc.
• Inventors: Baker, David Marvin, Gold, Steven Allen
• Granted Patent: US 7,493,335 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A computer software system is provided, namely An Object Process Graph Relational Database Interface (OPGRDI) system. The OPGRDI defines and updates relational database tables based on an OPG and stores and retrieves data in the tables as an OPG-defined application is run. The OPGRDI also defines and updates OPG persistent data object elements based on relational database table schemas. The OPGRDI functions can be enabled by users who want to store and retrieve application information in a relational database system, such as Oracle, Sybase, SQL Server, etc. The OPGRDI alters relational database tables as a user changes the structure of OPG-defined application.

Claims

1. An object process graph relational database interface system, comprising:

a relational database table definer for creating at least one schema that is storable in a relational database management system corresponding to at least one object process graph.

2. The system of claim 1, further comprising:

a graph data change recorder for creating a plurality of descriptions of changes to said at least one object process graph, said descriptions being grouped by transaction;

at least one journal for holding said descriptions; and

a relational database updater for selectively storing said descriptions in said relational database management system, said relational database updater having a transaction processor and a row writer, said transaction processor for determining which descriptions are in a particular transaction and determining an order for said selective storing, said row writer for determining whether a row is to be inserted or updated in a particular table in said relational database management system.

3. The system of claim 1, wherein said relational database updater is capable of running on a separate process thread.

4. The system of claim 1, further comprising:

a graph data retriever for retrieving composite data node attribute values from said relational database management system and for providing composite data nodes for data loading into an object process graph.

5. The system of claim 4, wherein said graph data retriever is capable of creating an instance of a composite data node retriever, said composite data node retriever running on a requestor'"'"'s thread, said composite data node retriever being capable of handling multiple requests for composite data nodes concurrently, said graph data retriever including a row reader for accessing said relational database management system.

6. The system of claim 1, further comprising:

a graph data object definer for creating at least one description corresponding to said at least one schema; and

an object process graph system for importing said at least one description.

7. The system of claim 6, wherein said at least one description includes a plurality of tables,

each table corresponding to a composite data node in said at least one object process graph,

said composite data node having an instance number attribute representing an identifier, and

said table including columns, each column corresponding to a primitive data node in said at least one object process graph.

8. The system of claim 7, wherein said plurality of tables includes a first table and a second table,

said first table being in a one-to-one relationship to said second table,

said first table corresponding to a first composite data node and said second table corresponding to a second composite data node, and

said first composite data node being in a parent-child relationship to said second composite data node.

9. The system of claim 7, wherein said plurality of tables includes a first table and a second table,

said first table having a foreign key column that references said second table,

said first table corresponding to a first composite data node and said second table corresponding to a second composite data node, and

said first composite data node having a reference node, said reference node being associated with said second composite data node.

10. The system of claim 7, wherein said plurality of tables includes a first table and a second table,

said first table being in a one-to-many relationship with said second table,

said first table corresponding to a first composite data node,

said first composite data node having a data array node, and

said data array node having an array of second composite data nodes corresponding to said second table.

11. The system of claim 7, wherein said plurality of tables includes a first table, a second table, and a third table,

said first table being in a many-to-many relationship with said third table,

said second table connecting said first and third tables,

said first table corresponding to an array of first composite data nodes,

said first composite data nodes being associated with a first data array node,

said first data array node having an array of third composite data nodes corresponding to said third table,

said array of third composite data nodes being associated with a second data array node, and

said second data array node being associated with said array of first composite data nodes.

12. A software product stored as instructions on a storage medium for performing a method of providing an object process graph relational database interface, the method comprising:

creating at least one schema that is storable in a relational database management system corresponding to at least one object process graph;

creating a plurality of descriptions of changes to said at least one object process graph, said descriptions being grouped by transaction; and

selectively storing said descriptions in said relational database management system.

13. The software product of claim 12, wherein the method further comprises:

creating at least one description corresponding to said at least one schema; and

importing said at least one description.

14. The software product of claim 13, wherein said at least one description includes a plurality of tables,

each table corresponding to a composite data node in said at least one object process graph,

said composite data node having an instance number attribute representing an identifier, and

said table including columns, each column corresponding to a primitive data node in said at least one object process graph.

15. The software product of claim 14, wherein said plurality of tables includes a first table and a second table,

said first table being in a one-to-one relationship to said second table,

said first table corresponding to a first composite data node and said second table corresponding to a second composite data node, and

said first composite data node being in a parent-child relationship to said second composite data node.

16. The software product of claim 14, wherein said plurality of tables includes a first table and a second table,

said first table having a foreign key column that references said second table,

said first table corresponding to a first composite data node and said second table corresponding to a second composite data node, and

said first composite data node having a reference node, said reference node being associated with said second composite data node.

17. The software product of claim 14, wherein said plurality of tables includes a first table and a second table,

said first table being in a one-to-many relationship with said second table,

said first table corresponding to a first composite data node,

said first composite data node having a data array node, and

said data array node having an array of second composite data nodes corresponding to said second table.

18. The software product of claim 14, wherein said plurality of tables includes a first table, a second table, and a third table,

said first table being in a many-to-many relationship with said third table,

said second table connecting said first and third tables,

said first table corresponding to an array of first composite data nodes,

said first composite data nodes being associated with a first data array node,

said first data array node having an array of third composite data nodes corresponding to said third table,

said array of third composite data nodes being associated with a second data array node, and

said second data array node being associated with said array of first composite data nodes.

19. A method of providing an object process graph relational database interface, comprising:

receiving at least one object process graph;

creating at least one schema corresponding to said at least one object process graph;

providing at least one schema corresponding to said object process graph; and

storing said at least one schema associated with said object process graph in a relational database.

20. The method of claim 19, further comprising:

creating at least one description corresponding to said at least one schema; and

importing said at least one description.