System and method for object persistence in a database store
First Claim
1. A computer-implemented method for persisting an object in a database store, comprising:
- creating a definition of a user-defined type of an object that is persisted in the database store, wherein the definition of the user-defined type comprises fields and methods, each field of the definition of the type user-defined comprising one or more storage facets;
annotating at least one field of the definition of the user-defined type with a first attribute that controls said one or more storage facets of the field;
annotating at least one method with a second attribute that denotes an equivalent structural access path; and
wherein the database store uses the annotations in the definition of the user-defined type to control the storage layout of instances of the user-defined type in the database store.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
4 Claims
-
1. A computer-implemented method for persisting an object in a database store, comprising:
-
creating a definition of a user-defined type of an object that is persisted in the database store, wherein the definition of the user-defined type comprises fields and methods, each field of the definition of the type user-defined comprising one or more storage facets; annotating at least one field of the definition of the user-defined type with a first attribute that controls said one or more storage facets of the field; annotating at least one method with a second attribute that denotes an equivalent structural access path; and wherein the database store uses the annotations in the definition of the user-defined type to control the storage layout of instances of the user-defined type in the database store. - View Dependent Claims (2, 3, 4)
-
Specification