← Back to Patent Explorer
US6076090A Expired / Lapsed US ⏱️ 0.0 years remaining

Default schema mapping

Assignee: International Business Machines Corp
•
Filing: 1997-11-26
•
Granted: 2000-06-13
•
Expires: 2017-11-26
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A method and system for persisting an object in a relational database schema by creating a new relational table at application program run-time for each class of objects to be persisted. The method may generate a schema map object for each class of objects to be persisted. The schema map object may be generated in response to the first transaction in which an object of a certain class is to be persisted and remains in memory for persisting, querying, restoring or deleting objects of that class. The schema map object determines the fields of each class of objects to be persisted, defines one or more columns in the table in accordance with the data types of the fields, and controls the passing of data between the table and the object fields.

Inventors

  • 👤 Tracy Kim Burroughs
  • 👤 Steven John Gansemer
  • 👤 Wilson D. Lee
  • 👤 Vance Palmer Morrison
  • 👤 Cynthia Ann Rogers
  • 👤 Laura Jane Zaborowski

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-30 02:31
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/44; G06F9/448; G06F9/4488; G06F9/4493; G06F16/00; G06F16/20; G06F16/28; G06F16/289; Y; Y10; Y10S; Y10S707/00; Y10S707/953; Y10S707/954; Y10S707/955; Y10S707/99941; Y10S707/99943

Claims Analysis

Total Claims: 38
Claim 1
Independent Claim 99 words
A computer-implemented method for persisting an object in a relational database at an application program run-time, the method comprising the steps of: determining fields of said object; creating in a relational database a row corresponding to said object and one or more columns corresponding to said fields; creating a schema map object, said schema-map object defining a mapping between said fields of said object and said columns; unencapsulating said object to read values of said fields; and storing said values of said fields in said columns to which said fields are mapped in accordance with said schema map object.
Claim 2
Dependent Claim 99 words
A computer-implemented method for persisting an object in a relational database at an application program run-time, the method comprising the steps of: determining fields of said object; creating in a relational database a row corresponding to said object and one or more columns corresponding to said fields; creating a schema map object, said schema-map object defining a mapping between said fields of said object and said columns; unencapsulating said object to read values of said fields; and storing said values of said fields in said columns to which said fields are mapped in accordance with said schema map object.
Claim 3
Dependent Claim 34 words
The computer-implemented method recited in claim 1, wherein said step of determining fields of said object comprises the step of obtaining a field name, a field type, and a class name of each field.
Claim 4
Dependent Claim 31 words
The computer-implemented method recited in claim 1, wherein said step of determining fields of said object comprises the step of referencing a class object of which said object is an instance.
Claim 5
Dependent Claim 27 words
The computer-implemented method recited in claim 3, wherein said step of determining fields of said object comprises the step of invoking reflections methods on said class object.
Claim 6
Dependent Claim 36 words
The computer-implemented method recited in claim 1, wherein said step of unencapsulating said object comprises the steps of: said schema map object calling a native method; and said native method reading each field, including private fields.
Claim 7
Dependent Claim 34 words
The computer-implemented method recited in claim 5, wherein said native method is written in a language other than a language in which said object is written that can access private fields of said object.
Claim 8
Dependent Claim 58 words
The computer-implemented method recited in claim 1, further comprising the steps of: creating in said relational database an object identifier column designated as a primary key; determining an object identifier associated with said object, said object identifier uniquely identifying said object against all other objects in a framework; and storing said object identifier in said object identifier column.
Claim 9
Dependent Claim 34 words
The computer-implemented method recited in claim 7, wherein said step of determining an object identifier associated with said object comprises the step of reading an object identifier field of a handle referencing said object.
Claim 10
Dependent Claim 49 words
The computer-implemented method recited in claim 1, further comprising the steps of: determining whether any of said fields is declared to be of a predetermined data type; and streaming all fields of said object to a single column if any field is declared to be of said predetermined type.
Claim 11
Dependent Claim 20 words
The computer-implemented method recited in claim 9, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 12
Dependent Claim 100 words
The computer-implemented method recited in claim 1, further comprising the steps of: identifying any fields of said object representing a contained object; determining fields of said contained object; creating one or more columns corresponding to said fields of said contained object, said schema-map object defining a mapping between each field of said contained object and one of said columns; unencapsulating said contained object to read values of said fields of said contained object; and storing said values of said fields of said contained object in said columns to which said fields are mapped in accordance with said schema map object.
Claim 13
Dependent Claim 54 words
The computer-implemented method recited in claim 11, further comprising the steps of: determining whether any of said fields of said contained object is declared to be of a predetermined data type; and streaming all fields of said contained object to a single column if any field is declared to be of said predetermined type.
Claim 14
Dependent Claim 20 words
The computer-implemented method recited in claim 12, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 15
Dependent Claim 40 words
The computer-implemented method recited in claim 1, further comprising the steps of: determining whether any of said fields of said object represents an embedded handle referencing another object; and streaming all fields of said embedded handle to a single column.
Claim 16
Dependent Claim 123 words
A computer-implemented method for persisting an object in a relational database at an application program run-time, the method comprising the steps of: referencing a class object of which said object is an instance to determine fields of said class object; creating in a relational database a row corresponding to said object and one or more columns corresponding to said fields; creating a schema map object, said schema-map object defining a mapping between said fields of said object and said columns; said schema map object calling a native method; said native method reading each field, including private fields of said object; and storing said values of said fields in said columns to which said fields are mapped in accordance with said schema map object.
Claim 17
Dependent Claim 123 words
A computer-implemented method for persisting an object in a relational database at an application program run-time, the method comprising the steps of: referencing a class object of which said object is an instance to determine fields of said class object; creating in a relational database a row corresponding to said object and one or more columns corresponding to said fields; creating a schema map object, said schema-map object defining a mapping between said fields of said object and said columns; said schema map object calling a native method; said native method reading each field, including private fields of said object; and storing said values of said fields in said columns to which said fields are mapped in accordance with said schema map object.
Claim 18
Dependent Claim 105 words
A program product for use in a computer system, said program product for persisting an object in a relational database, said computer program product comprising a signal-bearing medium carrying thereon: a schema map constructor defining a schema map object having a method for determining fields of said object, a method for initiating creation in a relational database a row corresponding to said object and one or more columns corresponding to said fields, and a method for initiating storage of values read from said fields in said columns; a native interface; and a native method for unencapsulating said object to read said values of said fields.
Claim 19
Dependent Claim 105 words
A program product for use in a computer system, said program product for persisting an object in a relational database, said computer program product comprising a signal-bearing medium carrying thereon: a schema map constructor defining a schema map object having a method for determining fields of said object, a method for initiating creation in a relational database a row corresponding to said object and one or more columns corresponding to said fields, and a method for initiating storage of values read from said fields in said columns; a native interface; and a native method for unencapsulating said object to read said values of said fields.
Claim 20
Dependent Claim 60 words
The program product recited in claim 16, wherein said schema map object creates in said relational database an object identifier column designated as a primary key, determines an object identifier associated with said object, said object identifier uniquely identifying said object against all other objects in a framework, and initiates storage of said object identifier in said object identifier column.
Claim 21
Dependent Claim 23 words
The program product recited in claim 17, wherein said schema map object reads an object identifier field of a handle referencing said object.
Claim 22
Dependent Claim 51 words
The program product recited in claim 16, wherein said schema map object determines whether any of said fields is declared to be of a predetermined data type and initiates streaming of all fields of said object to a single column if any field is declared to be of said predetermined type.
Claim 23
Dependent Claim 20 words
The program product recited in claim 19, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 24
Dependent Claim 76 words
The program product recited in claim 16, wherein: said schema map object identifies any fields of said object representing a contained object, determines fields of said contained object, initiates creation of one or more columns corresponding to said fields of said contained object, and initiates storage of values of said fields of said contained object in said columns; and said native method unencapsulates said contained object to read values of said fields of said contained object.
Claim 25
Dependent Claim 54 words
The program product recited in claim 21, wherein said schema map object determines whether any of said fields of said contained object is declared to be of a predetermined data type and streams all fields of said contained object to a single column if any field is declared to be of said predetermined type.
Claim 26
Dependent Claim 20 words
The program product recited in claim 22, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 27
Dependent Claim 40 words
The program product recited in claim 16, wherein said schema map object determines whether any of said fields of said object represents an embedded handle referencing another object and streams all fields of said embedded handle to a single column.
Claim 28
Independent Claim 105 words
A system for persisting an object in a relational database at an application program run-time, comprising: a relational database; a container object for referencing said object in response to said application program completing a transaction; and a schema map constructor defining a schema map object having a method for determining fields of said object, a method for initiating creation in a relational database a row corresponding to said object and one or more columns corresponding to said fields, a method for unencapsulating said object to determine values of said fields, and a method for initiating storage of values read from said fields in said columns.
Claim 29
Independent Claim 105 words
A system for persisting an object in a relational database at an application program run-time, comprising: a relational database; a container object for referencing said object in response to said application program completing a transaction; and a schema map constructor defining a schema map object having a method for determining fields of said object, a method for initiating creation in a relational database a row corresponding to said object and one or more columns corresponding to said fields, a method for unencapsulating said object to determine values of said fields, and a method for initiating storage of values read from said fields in said columns.
Claim 30
Dependent Claim 30 words
The system recited in claim 25, wherein said schema map object comprises: a native interface; and a native method for unencapsulating said object to read said values of said fields.
Claim 31
Dependent Claim 59 words
The system recited in claim 25, wherein said schema map object creates in said relational database an object identifier column designated as a primary key, determines an object identifier associated with said object, said object identifier uniquely identifying said object against all other objects in a framework, and initiates storage of said object identifier in said object identifier column.
Claim 32
Dependent Claim 22 words
The system recited in claim 27, wherein said schema map object reads an object identifier field of a handle referencing said object.
Claim 33
Dependent Claim 50 words
The system recited in claim 25, wherein said schema map object determines whether any of said fields is declared to be of a predetermined data type and initiates streaming of all fields of said object to a single column if any field is declared to be of said predetermined type.
Claim 34
Dependent Claim 19 words
The system recited in claim 29, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 35
Dependent Claim 75 words
The system recited in claim 25, wherein: said schema map object identies any fields of said object representing a contained object, determines fields of said contained object, initiates creation of one or more columns corresponding to said fields of said contained object, and initiates storage of values of said fields of said contained object in said columns; and said native method unencapsulates said contained object to read values of said fields of said contained object.
Claim 36
Dependent Claim 53 words
The system recited in claim 31, wherein said schema map object determines whether any of said fields of said contained object is declared to be of a predetermined data type and streams all fields of said contained object to a single column if any field is declared to be of said predetermined type.
Claim 37
Dependent Claim 19 words
The system recited in claim 32, wherein said type is selected from the group consisting of: vector and hashtable.
Claim 38
Dependent Claim 39 words
The system recited in claim 25, wherein said schema map object determines whether any of said fields of said object represents an embedded handle referencing another object and streams all fields of said embedded handle to a single column.

References Cited (Backward Citations)

US5295256A Cited
US5291583A Cited
US5613099A Cited
US5499371A Cited
US5729739A Cited
US5627979A Cited
US5542078A Cited
US5694598A Cited
US5873093A Cited
US5850544A Cited
US5878411A Cited
US5956730A Cited
US5956725A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2003-06-13 2003-12-13 2004-06-13 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2007-06-13 2007-12-13 2008-06-13 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2011-06-13 2011-12-13 2012-06-13 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag