Incremental approach to an object-relational solution

• US 7,676,493 B2
• Filed: 02/28/2006
• Issued: 03/09/2010
• Est. Priority Date: 09/07/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Henry, Alyssa Heather, Suver, Chris A., Muralidhar, Subramanian, Pizzo, Michael J., Albahari, Benjamin, Conrad, Andrew J., Blakeley, Jose A., Castro, Pablo
• Primary Examiner(s): Ali; Mohammad
• Assistant Examiner(s): Smith; Brannon W
• Application Number:
  US11/364,060
• Publication Number:
  US 20070055692A1
• Time in Patent Office: 1,470 Days
• Field of Search: 707/103, 707/E17.005
• US Class Current: 707/796
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

The claimed subject matter relates to an architecture that can facilitate an incremental approach to an Object-Relational mapping solution. The architecture can provide a rich data model that is defined at the value layer. The rich data model can expose an interface that conforms with the interfaces exposed by common storage-specific data providers. The architecture can extend common storage-specific data provider to support common command representations, and provide entity services that work in terms of the rich data model as well as object services such as identity management, updating and change tracking.

Claims

1. A system that facilitates an incremental approach to object-relational mapping by providing functionality, that is typically found in an object layer, on top of an existing value layer API, the system comprising the following components:

a storage-specific provider component that exposes an API at a value layer of the system for accessing data within a data store, the API conforming with a common data model such that requests made through the API include a connection, a command, and a result object, wherein data returned by the storage-specific provider component is formatted as flat relational data;

a mapping provider component that maps the data returned by the storage-specific provider component to a rich relational schema, the rich relational schema defining a format for the data that includes hierarchical and inheritance information, but without materializing the data as an object, the mapping provider component further exposing a rich schema API at the value layer through which the data formatted according to the rich relational schema is retrieved, the rich schema API conforming with the common data model such that requests made through the rich schema API include a connection, a command, and a result object such that requests for data may be made through the API exposed by the storage-specific provider component or the rich schema API exposed by the mapping provider component using the same API calls at the value layer;

an object layer object mapping component that maps data returned by the mapping provider component to an object schema in accordance with the common data model, wherein a processor operatively coupled to memory implements the storage-specific provider component, the mapping component and the object layer object mapping component; and

a value layer services component that operates in terms of the common data model, wherein the value layer services comprise at least one of returning results with inheritance, returning associations within results, or returning compositions within results without materializing a class representing the value, and wherein the value layer services component includes a common component that compensates for a command operator not supported by the data store.

2. The system of claim 1, the common data model includes an entity, the entity is at least one of an entity with strong identity, an entity with inheritance, an entity with complex types, and an entity with relationships.

3. The system of claim 1, the command operator includes a representation of nested results.

4. The system of claim 1, the services component includes a cache.

5. The system of claim 4, the cache is employed for at least one of identity management and change tracking.

6. The system of claim 1, the object services includes at least one of a typed query, or data aggregation.

7. The system of claim 1, the object layer object mapping component exposes an object API conforming with the common data model such that requests made through the object API include a connection, a command, and a result object such that requests for data may be made through the API exposed by the storage-specific provider component or the object API using the same API calls at the value layer.

8. The system of claim 1, further including a common metadata service component that describes the common data model and supports services that require metadata.

9. The system of claim 1, the storage-specific provider component is extended to support a common command representation.

10. The system of claim 1, the storage-specific provider component is extended to compensate for a command operator not supported by the data store.

11. The system of claim 10, the command operator includes a representation of nested results.

12. The system of claim 1, the object layer object mapping component receives mapping information by reflecting on properties of the type being materialized.

13. The system of claim 1, the mapping provider component gets mapping information from an object mapping loaded from one of a file or a data store.

14. A computer storage medium having stored thereon the following computer executable components:

a storage-specific provider component that exposes an API at a value layer of a computer system for accessing data within a data store, the API conforming with a common data model such that requests made through the API include a connection, a command, and a result object, wherein data returned by the storage-specific provider component is formatted as flat relational data;

a mapping provider component that maps the data returned by the storage-specific provider component to a rich relational schema, the rich relational schema defining a format for the data that includes hierarchical and inheritance information, but without materializing the data as an object, the mapping provider component further exposing a rich schema API at the value layer through which the data formatted according to the rich relational schema is retrieved, the rich schema API conforming with the common data model such that requests made through the rich schema API include a connection, a command, and a result object such that requests for data may be made through the API exposed by the storage-specific provider component or the rich schema API exposed by the mapping provider component using the same API calls at the value layer;

an object layer object mapping component that maps data returned by the mapping provider component to an object schema in accordance with the common data model, wherein a processor operatively coupled to memory implements the storage-specific provider component, the mapping component and the object layer object mapping component; and

a value layer services component that operates in terms of the common data model, wherein the value layer services comprise at least one of returning results with inheritance, returning associations within results, or returning compositions within results without materializing a class representing the value, and wherein the value layer services component includes a common component that compensates for a command operator not supported by the data store.