US5937402A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System for enabling access to a relational database from an object oriented program
Assignee: DATATERN Inc
•
Filing: 1997-06-19
•
Granted: 1999-08-10
•
Expires: 2017-06-19
Abstract
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.
Inventors
- 👤 Jayant G. Pandit
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-06 19:42
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/25; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99932; Y10S707/99933; Y10S707/99934
Claims Analysis
Total Claims: 29
Claim 1
Independent Claim
135 words
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.
Claim 2
Independent Claim
135 words
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.
Claim 3
Dependent Claim
44 words
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.
Claim 4
Dependent Claim
18 words
The method of claim 1 including the further step of supplying a discriminator constraint for the logical table.
Claim 5
Independent Claim
163 words
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.
Claim 6
Independent Claim
163 words
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.
Claim 7
Dependent Claim
21 words
The apparatus of claim 4 wherein the at least one of the one or more physical tables is a denormalized table.
Claim 8
Dependent Claim
45 words
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.
Claim 9
Dependent Claim
15 words
The apparatus of claim 4 further including a discriminator constraint associated with the logical table.
Claim 10
Independent Claim
87 words
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.
Claim 11
Independent Claim
87 words
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.
Claim 12
Dependent Claim
52 words
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.
Claim 13
Dependent Claim
27 words
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.
Claim 14
Dependent Claim
13 words
The method of claim 10, wherein said object oriented programming language is C++.
Claim 15
Dependent Claim
14 words
The method of claim 10, wherein said at least one type definition is predefined.
Claim 16
Dependent Claim
18 words
The method of claim 8, wherein said subset of said columns of said physical table is user defined.
Claim 17
Dependent Claim
35 words
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.
Claim 18
Independent Claim
104 words
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.
Claim 19
Independent Claim
104 words
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.
Claim 20
Independent Claim
98 words
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.
Claim 21
Independent Claim
98 words
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.
Claim 22
Independent Claim
111 words
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.
Claim 23
Independent Claim
111 words
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.
Claim 24
Independent Claim
145 words
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.
Claim 25
Independent Claim
145 words
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.
Claim 26
Independent Claim
92 words
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.
Claim 27
Independent Claim
92 words
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.
Claim 28
Independent Claim
108 words
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.
Claim 29
Independent Claim
108 words
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.
References Cited (Backward Citations)
US4525780A
Cited
US5283894A
Cited
US5010478A
Cited
US5206951A
Cited
US5008853A
Cited
US4853843A
Cited
US5142674A
Cited
US4864497A
Cited
US4953080A
Cited
US5079695A
Cited
US5185885A
Cited
US5175848A
Cited
US4989132A
Cited
US5227967A
Cited
US5113522A
Cited
US5125091A
Cited
US5129084A
Cited
US5136712A
Cited
US5187790A
Cited
US5129083A
Cited
US5187787B1
Cited
US5187787A
Cited
US5170466A
Cited
US5161225A
Cited
US5161223A
Cited
US5093914A
Cited
US5157777A
Cited
US5191522A
Cited
US5369761A
Cited
US5265206A
Cited
US5327559A
Cited
US5291593A
Cited
US5295256A
Cited
US5291583A
Cited
US5187786A
Cited
US5193180A
Cited
US5386564A
Cited
US5701453A
Cited
US5499371A
Cited
US5388264A
Cited
US5542078A
Cited
US5734887A
Cited
US5778375A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-08-09 | 2003-02-08 | 2003-08-10 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-08-09 | 2007-02-08 | 2007-08-10 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-08-09 | 2011-02-08 | 2011-08-10 | $7700.00 | Window Closed / Lapsed |