Method and apparatus for mapping objects to multiple tables of a database

• US 6,122,641 A
• Filed: 02/12/1999
• Issued: 09/19/2000
• Est. Priority Date: 12/07/1994
• Status: Expired due to Term

• Current Assignee: Next Software Incorporated (Apple Inc.)
• Original Assignee: Next Software Incorporated (Apple Inc.)
• Inventors: Williamson, Richard, Upson, Linus, Greenfield, Jack, Willhite, Daniel
• Primary Examiner(s): Alam, Hosain T.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US09/249,465
• Time in Patent Office: 585 Days
• Field of Search: 707/103, 707/3, 707/101, 707/102
• US Class Current: 707/793
• CPC Class Codes: G06F 16/2438 Embedded query languages
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• 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

The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application'"'"'s object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship. A flattened attribute is an attribute of one entity that is added to another entity. A flattened relationship is created by the elimination of intermediate relationships between two entities. Relationships can be either unidirectional or bi-directional. A unidirectional relationship has a single traversal path that has a source entity and a destination. A bi-directional relationship has two traversal paths. A reflexive relationship can be created using a single entity. The model is used to synchronize object properties and the data of the data source.

Claims

1. A method of mapping object transparently to a data source stored in a storage medium in a computer system comprising the steps of:

independently defining an object class;

independently defining a schema for said data source, said schema defining being independent of said object class defining; and

defining a model providing a mapping between properties of said object class and data of said data source schema, such that the mapping between said data source schema and said object class is transparent to said object class and said data source schema.

2. The method of claim 1 wherein said data source schema is a database schema.

3. The method of claim 2 wherein said model is comprised of at least one entity that has at least one attribute.

4. The method of claim 3 wherein said attribute is a simple attribute that maps directly to an item of data in said data source.

5. The method of claim 3 wherein said attribute is a derived attribute that does not directly map to an item of data in said data source.

6. The method of claim 3 wherein said model has a plurality of entities and a plurality of relationships between at least two of said plurality of entities.

7. The method of claim 1 further comprising the steps of:

defining a first entity of said model having a first attribute;

defining a second entity of said model;

defining a relationship between said first and second entities; and

using said relationship to define said first attribute as an attribute of said second entity.

8. The method of claim 1 further comprising the steps of:

defining a first entity of said model;

defining a second entity of said model;

defining a first relationship between said first and second entities;

defining a third entity of said model;

defining a second relationship between said second and third entities; and

defining a third relationship between said first and third entities using said first and second relationships.

9. A method of mapping an object transparently to a table of a database stored in a storage medium in a computer system comprising the steps of:

independently defining a property for an object class;

independently defining a first table having one or more attributes, said first table defining being independent of said property defining;

defining a model having an entity that corresponds with said first table;

defining in said entity a flattened attribute, said flattened attribute being an attribute of a second entity that corresponds with a second table; and

associating said object with said first entity thereby associating said object with said first table and said second table.

10. The method of claim 9 further comprising the steps of:

generating, using said first entity'"'"'s definition, a statement to fetch a record from a database;

instantiating an instance of said object class and loading said property of said instance with a data value contained in said record;

modifying said property using one or more methods of said object; and

using said first entity'"'"'s definition to propagate said modification made by said object to said first and second tables.

11. An article of manufacture comprising:

a computer usable medium having computer readable program code embodied therein for mapping an object transparently to a data source comprising;

computer readable program code configured to cause a computer to independently define an object class;

computer readable program code configured to cause a computer to independently define a schema for said data source, said schema defining being independent of said object class defining; and

computer readable program code configured to cause a computer to create a mapping between said object class and said data source schema using a mapping model, said mapping between said data source schema and said object class transparent to said object class and said data source schema.

12. The article of manufacture of claim 11 wherein said object class includes a property, said program code configured to cause a computer to create further comprising:

computer readable program code configured to cause a computer to create and entity in said mapping model;

computer readable program code configured to cause a computer to relate said entity to said schema;

computer readable program code configured to cause a computer to create in said model an attribute for said entity; and

computer readable program code configured to cause a computer to relate said entity to said property.

13. The article of manufacture of claim 12 wherein said data source is a relational database having a table, said program code configured to cause a computer to relate further comprising:

computer readable program code configured to cause a computer to relate said entity to said table in said relational database.

14. The article of manufacture of claim 12 wherein said data source is a relational database having a table, said program code configured to cause a computer to relate said entity to said schema further comprising:

computer readable program code configured to cause a computer to relate said attribute of said entity to a column of said table in said relational database.

15. The article of manufacture of claim 11 wherein said mapping model includes a plurality of entities, each of said plurality of entities having a plurality of attributes and a plurality of relationships, wherein at least one of said relationships exists with at least one entity of said mapping model.

16. The article of manufacture of claim 11 wherein said mapping model includes a plurality of entities, each of said plurality of entities having a plurality of attributes and a plurality of relationships, wherein at least one of said plurality of relationships is a reflexive relationship that exists between two of said plurality of attributes in one of said plurality of entities.

17. The article of manufacture of claim 11 wherein said mapping model includes a plurality of entities, each of said plurality of entities having a plurality of attributes and a plurality of relationships, wherein at least one of said plurality of relationships is a flattened relationship that relates two of said plurality of entities via one or more intermediate entities.

18. The article of manufacture of claim 11 wherein said mapping model includes a plurality of entities, each of said plurality of entities having a plurality of attributes and a plurality of relationships, wherein one of said plurality of relationships relate s at least one of said plurality of objects to multiple schema entities of s aid data source.

19. The article of manufacture of claim 18 wherein a schema entity is a database table.

20. The article of manufacture of claim 18 further comprising:

computer readable program code configured to cause a computer to identify a first relationship key in a first of said plurality of entities;

computer readable program code configured to cause a computer to identify a second relationship key in a second if said plurality of said entities; and

computer readable program code configured to cause a computer to define a traversal path using said first and second relationship keys.