Multi-model database management system engine for database having complex data models

• US 5,713,014 A
• Filed: 12/01/1995
• Issued: 01/27/1998
• Est. Priority Date: 09/21/1994
• Status: Expired due to Fees

• Current Assignee: Micro Data Base Systems, Inc.
• Original Assignee: Micro Data Base Systems, Inc.
• Inventors: Durflinger, Kevin, Logan, Kim M., Reid, Jon D.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Choules, Jack M.
• Application Number:
  US08/565,890
• Time in Patent Office: 788 Days
• Field of Search: 395/601, 395/604, 395/611, 395/613
• US Class Current: 1/1
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A multi-model database management system (DBMS) presents to its users a variety of logical models, or views of stored data, using industry-standard interfaces, while the physical storage of data is managed in a manner that closely follows the data model. Databases are built from sets of records using the entity-relationship data model. Space is reserved in each owner record for a set pointer pointing to either a member record or a Dynamic Pointer Array (DPA) structure that relates the owner record to member records. The DPA itself contains set pointers to all of the related member records. Each member record, in turn, has a set pointer pointing back to a particular owner record, or, in certain instances, to another DPA. In such cases, the DPA contains set pointers pointing to all of the related owner records. The DBMS supports a variety of logical models including the relational model, and further supports a plurality of industry-standard Application Program Interfaces using SQL query access language.

Claims

1. A computer database management system for storing, retrieving and modifying complex data stored in a database, said system comprising:

a number of application processes, each of said application processes including;

a user accessible external application; and

one of a multiplicity of application program

interfaces for translating complex input data from said external application into a predefined intermediate data format and for translating said predefined intermediate data format into complex output data for said external application;

a first schema coupled to said number of application processes, said first schema translating said predefined intermediate data format into one of a plurality of logical data model formats and for translating said plurality of logical data model formats into said intermediate data format;

a second schema coupled to said first schema, said second schema defining a conceptual data model for translating said plurality of logical data model formats into a conceptual data format and for translating said conceptual data format into one of said logical data model formats; and

a database server including storage means for storing and retrieving the complex data objects in and from the database, said server storing and retrieving the data objects according to said conceptual data format, said storage means including;

a number of files, each of said files occupying a unique location within said storage means;

a number of pages associated with each of said files, said pages being variable in number within each of said files, each of said variable number of pages occupying a unique location within each of said number of files and having an object portion for storing at least one of said database objects and a header portion for storing at least one offset number, each of said offset numbers occupying a unique location within said header and corresponding to one of said database objects stored on said page;

a database key portion for storing a database key associated with each of said database objects, said database key including a page identification portion for identifying a unique one of said pages containing said database object and an object identification portion for identifying said unique location within said header portion of said unique page containing said offset number corresponding to said database object,

wherein any of said database objects contained on said unique one of said pages within one of said number of files is stored at a location within said unique page determined by adding said offset number corresponding to said database object to the starting location of said unique page.

2. The system of claim 1 wherein the particular one of said number of files associated with said unique one of said pages containing said database object is inherent in said page identification portion of said database key of said database object.

3. The system of claim 2, wherein said page identification portion of said database key is a page number.

4. The system of claim 3, wherein said object identification portion of said database key is an object number.

5. The system of claim 4, wherein said database object includes a data record.

6. The system of claim 5, wherein said data record includes one of principal fragments and tributary fragment pointers.

7. The system of claim 6, wherein said data record includes the other of principal fragments and tributary fragment pointers.

8. The system of claim 3, wherein said data record further includes set pointers, said set pointers pointing to at least one of said plurality of database objects.