System for enabling access to a relational database from an object oriented program

• US 5,937,402 A
• Filed: 06/19/1997
• Issued: 08/10/1999
• Est. Priority Date: 06/19/1997
• Status: Expired due to Term

• Current Assignee: DataTern Incorporated
• Original Assignee: Ontos
• Inventors: Pandit, Jayant G.
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): Homere, Jean R.
• Application Number:
  US08/879,241
• Time in Patent Office: 782 Days
• Field of Search: 707/2, 707/3, 707/4, 707/100, 707/103
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

Logical tables and logical keys are employed to facilitate interaction between user applications and a relational database. Each logical table is a group of at least one column from a table or view associated with a relational database, and can be utilized like a relational table or view. Each logical primary or foreign key is a key between logical and physical tables that behaves like an actual primary or foreign key. A normalization process allows creation of integrator relational schema objects from existing captured tables. Once a denormalized table is captured from a database the normalization process allows the user to define different logical tables using subsets of the columns of the table. One or more columns of the logical table are designated as primary key. The logical tables interact with the mapping process in the same manner as physical tables.

Claims

1. A method for enabling an object oriented user application to access a relational database having one or more physical tables segmented into rows and columns, comprising:

defining a logical table comprising a subset of columns from at least one of the one or more physical tables;

designating one column of the logical table as a logical primary key column;

forming a normalized relational schema object representing the logical table;

generating, responsive to the normalized relational schema object, one or more object classes associated with the normalized relational schema object; and

employing an object of an object class including the one or more object classes associated with the normalized relational schema object and a respective corresponding logical primary key value to access data in the at least one of the physical tables in the relational database.

2. The method of claim 1 including the further step of employing normalization to create foreign key relationships from a first of the one or more physical tables or the logical table to another physical or logical table having a physical or logical primary key.

3. The method of claim 1 including the further step of supplying a discriminator constraint for the logical table.

4. An apparatus for facilitation of data exchange between an object oriented user application and a relational database having one or more physical tables segmented into rows and columns, comprising:

an integrator operative to define a logical table comprising a subset of columns from at least one of the one or more physical tables, the integrator being further operative to designate at least one column of the logical table as a logical primary key column, and being further operative to form a normalized relational schema object representing the logical table, and being further operative, responsive to said normalized relational schema object, to generate one or more object classes associated with said normalized relational schema object; and

a repository which employs the one or more object classes and the logical table and respective corresponding logical primary key values to facilitate access of data in the at least one of the one or more physical tables in the relational database by the object oriented user application.

5. The apparatus of claim 4 wherein the at least one of the one or more physical tables is a denormalized table.

6. The apparatus of claim 5 further comprising a normalization processor operative to create foreign key relationships from the at least one of the one or more physical tables or the logical table to another physical or logical table having a physical or logical primary key.

7. The apparatus of claim 4 further including a discriminator constraint associated with the logical table.

8. A method for enabling access to a relational database from an object oriented program, comprising:

capturing one or more denormalized relational schema from said relational database, said one or more relational schema corresponding to a physical table segmented into rows and columns;

forming a normalized relational schema object representing a logical table, said logical table comprising a subset of said columns of said physical table; and

generating, responsive to said normalized relational schema object, one or more object class definitions associated with said normalized relational schema object.

9. The method of claim 8, further comprising:

creating, responsive to said capturing said one or more denormalized relational schema from said relational database, a respective one or more denormalized relational schema objects; and

wherein said forming said normalized relational schema object is responsive to said one or more denormalized relational schema objects.

10. The method of claim 8, wherein said one or more object class definitions are represented by at least one type definition for an object oriented programming language.

11. The method of claim 10, wherein said object oriented programming language is C++.

12. The method of claim 10, wherein said at least one type definition is predefined.

13. The method of claim 8, wherein said subset of said columns of said physical table is user defined.

14. The method of claim 8, wherein an identity of said normalized relational schema object is defined by a primary key constraint in one or more of said subset of said columns of said physical table.

15. A method for enabling access to a relational database from an object oriented program, comprising:

inputting a predetermined one or more denormalized relational schema objects, said set of one or more denormalized relational schema objects corresponding to a physical table in said relational database segmented into rows and columns;

forming a normalized schema object, responsive to said one or more denormalized relational schema objects, said normalized relational schema object representing a logical table comprising a subset of said columns of said physical table; and

generating, responsive to said normalized relational schema object, one or more object classes associated with said normalized relational schema object.

16. A system for enabling access to a relational database from an object oriented program, comprising:

a capture process for capturing one or more denormalized relational schema from said relational database, said one or more relational schema corresponding to a physical table segmented into rows and columns;

a normalization process for forming a normalized relational schema object representing a logical table, said logical table comprising a subset of said columns of said physical table; and

a mapping process for generating, responsive to said normalized relational schema object, one or more object classes associated with said normalized relational schema object.

17. A system for enabling access to a relational database from an object oriented program, comprising:

a normalization process for inputting one or more denormalized relational schema objects, said set of one or more denormalized relational schema objects corresponding to a physical table segmented into rows and columns, said normalization process further forming a normalized schema object, responsive to said set one or more denormalized relational schema objects, said normalized relational schema object representing a logical table comprising a subset of said columns of said physical table; and

a mapping process for generating, responsive to said normalized relational schema object, one or more object classes associated with said normalized relational schema object.

18. A system for enabling an object oriented user application to access a relational database having one or more physical tables segmented into rows and columns, comprising:

means for defining a logical table comprising a subset of columns from at least one of the one or more physical tables;

means for designating one column of the logical table as a logical primary key column;

means for forming a normalized relational schema object representing the logical table;

means for generating, responsive to the normalized relational schema object, one or more object classes associated with the normalized relational schema object; and

means for employing an object of an object class including the one or more object classes associated with the normalized relational schema object and a respective corresponding logical primary key value to access data in the at least one of the physical tables in the relational database.

19. A system for enabling access to a relational database from an object oriented program, comprising:

means for capturing one or more denormalized relational schema from said relational database, said one or more relational schema corresponding to a physical table segmented into rows and columns;

means for forming a normalized relational schema object representing a logical table, said logical table comprising a subset of said columns of said physical table; and

means for generating, responsive to said normalizing relational schema object, one or more object classes associated with said normalized relational schema object.

20. A system for enabling access to a relational database from an object oriented program, comprising:

means for inputting a predetermined set of one or more denormalized relational schema objects, said set one or more denormalized relational schema objects corresponding to a physical table segmented into rows and columns;

means for forming a normalized schema object, responsive to said set one or more denormalized relational schema objects, said normalized relational schema object representing a logical table comprising a subset of said columns of said physical table; and

means for generating, responsive to said normalized relational schema object, one or more object classes associated with said normalized relational schema object.