System and method for object persistence in a database store

• US 6,941,316 B2
• Filed: 10/23/2003
• Issued: 09/06/2005
• Est. Priority Date: 10/23/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sezgin, Beysim, Venkatesh, Ramachandran, Blakeley, Jose A., Altudov, Denis Y.
• Primary Examiner(s): Corrielus, Jean M.
• Application Number:
  US10/692,225
• Publication Number:
  US 20050091228A1
• Time in Patent Office: 684 Days
• Field of Search: 707/1, 707/3, 707/6, 707/7, 707/100, 707/101, 707/103.Y, 707/103, 707/102, 707/2, 717/11, 717/104, 717/122, 715/866
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24557 Efficient disk access during query execution
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99937 Sorting
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A new persistence format for storing objects of a user defined type in a database store enables information about the structure of the type to be communicated to the store. This information enables a number of store optimizations, including direct structural access to members of the type. Specifically, metadata is exchanged between the type implementer and the data store. The store uses the metadata to determine the storage layout for instances of the type. With this information, the store is able to detect access patterns that can be optimized to directly operate over the storage representation without hydration (deserialization) the object.

Claims

1. In a system in which an object that is an instance of a user defined type is persisted in a database store, wherein a definition of the user defined type comprises one or more fields and behaviors and includes annotations that control a storage layout for instances of the type in the database store, and wherein the database store maintains information reflecting the storage layout as provided by the annotations to the type definition, a method of executing a query on an object that is an instance of the type, the method comprising:

receiving a query on an object that is an instance of the type, wherein execution of the query may require hydration of the object;

accessing the information maintained by the database store to determine the storage layout of instances of the type;

translating the query into an equivalent structural access path for a value of a field of the type that is to be returned in response to the query, based on the information about the storage layout of instances of the type;

structurally accessing the value of the field without hydrating the object; and

returning the value of the field in response to the query.

2. The method recited in claim 1, wherein each field of the type is annotated with a first attribute that controls one or more storage facets of the field, and wherein each behavior is annotated with a second attribute that denotes an equivalent structural access path.

3. The method recited in claim 2, wherein the second attribute specifies the name of a field of the type that is the subject of the behavior.

4. The method recited in claim 1, wherein the storage facets of the field that are controlled by the first attribute comprise at least one of the maximum size of the field, whether or not the field is fixed length, the precision of the field, the scale of the field, and whether values of the field can be null.

5. The method of claim 1, wherein the object type is defined as a class in managed code.

6. A system comprising:

a database store in which an object that is an instance of a user defined type is persisted, wherein a definition of the user defined type comprises one or more fields and behaviors and includes annotations that control a storage layout for instances of the type in the database store, and wherein the database store maintains information reflecting the storage layout as provided by the annotations to the type definition; and

a database server that (i) receives a query on an object that is an instance of the user defined type, wherein execution of the query may require hydration of the object, (ii) accesses the information maintained by the database store to determine the storage layout of instances of the type, (iii) translates the query into an equivalent structural access path for a value of a field of the type that is to be returned in response to the query, based on the information about the storage layout of instances of the type, (iv) structurally accesses the value of the field without hydrating the object, and (v) returns the value of the field in response to the query.

7. The system recited in claim 6, wherein each field of the type is annotated with a first attribute that controls one or more storage facets of the field, and wherein each behavior is annotated with a second attribute that denotes an equivalent structural access path.

8. The system recited in claim 7, wherein the storage facets of the field that are controlled by the first attribute comprise at least one of the maximum size of the field, whether or not the field is fixed length, the precision of the field, the scale of the field, and whether values of the field can be null.

9. The system recited in claim 7, wherein the second attribute specifies the name of a field of the type that is the subject of the behavior.

10. The system recited in claim 6, wherein the object type is defined as a class in managed code.

11. A computer readable medium having program code stored thereon for use in a system in which an object that is an instance of a user defined type is persisted in a database store, wherein a definition of the user defined type comprises one or more fields and behaviors and includes annotations that control a storage layout for instances of the type in the database store, and wherein the database store maintains information reflecting the storage layout as provided by the annotations to the type definition, said program code, when executed on a computer, causing the computer to:

receive a query on an object that is an instance of the type, wherein execution of the query may require hydration of the object;

access the information maintained by the database store to determine the storage layout of instances of the type;

translate the query into an equivalent structural access path for a value of a field of the type that is to be returned in response to the query, based on the information about the storage layout of instances of the type;

structurally access the value of the field without hydrating the object; and

return the value of the field in response to the query.

12. The computer readable medium recited in claim 11, wherein each field of the type is annotated with a first attribute that controls one or more storage facets of the field, and wherein each behavior is annotated with a second attribute that denotes an equivalent structural access path.

13. The computer readable medium recited in claim 12, wherein the second attribute specifies the name of a field of the type that is the subject of the behavior.

14. The computer readable medium recited in claim 11, wherein the storage facets of the field that are controlled by the first attribute comprise at least one of the maximum size of the field, whether or not the field is fixed length, the precision of the field, the scale of the field, and whether values of the field can be null.

15. The computer readable medium of claim 11, wherein the object type is defined as a class in managed code.