Relationship serialization and reconstruction for entities

• US 9,940,353 B2
• Filed: 05/24/2017
• Issued: 04/10/2018
• Est. Priority Date: 06/26/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Parra, Sarah M., Vuppula, Ravinder R., Derstadt, Jeffrey M., Dawson, Brian, Pizzo, Michael J., Stone, III, James Madison, Magee, Patrick T., Poliakova, Nadejda V., Simmons, Daniel G.
• Primary Examiner(s): DWIVEDI, MAHESH H
• Application Number:
  US15/604,333
• Publication Number:
  US 20170262499A1
• Time in Patent Office: 321 Days
• Field of Search: 707609
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 16/245 Query processing

Abstract

Systems and methods that enable relationship information to be carried along with data objects when serializing/deserializing data objects among application tiers. A tracking component tracks information on relationships associated with a data object, and further enables subsequent change processing on the data object'"'"'s relationship information. Accordingly, relationship information can be carried along with the data object, such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Claims

1. A method, implemented at a computer system that includes one or more processors, the method comprising:

retrieving a data object;

serializing the data object; and

preserving relationships associated with the data object by attaching key information to the data object, and wherein a retrieval of a relationship varies according to whether a value included in the key information is null or non-null.

2. The method of claim 1, further comprising reconstructing a graph via serialized key information.

3. The method of claim 1, further comprising transferring the data object among various tiers of a database.

4. The method of claim 3, further comprising obtaining reference relationships for the data object from the database.

5. The method of claim 4, further comprising deserializing the data object.

6. The method of claim 4, further comprising mitigating a requirement to reload data objects from the database.

7. The method of claim 4, further comprising attaching the data object to a tracking context.

8. The method of claim 4, further comprising including information for the data object in a serialized pay load.

9. The method of claim 4, further comprising inferring a tracking of the data object via classifiers.

10. The method of claim 4, further comprising representing the data object through a proxy.

11. A hardware storage device having instructions stored thereon, the instructions configured to, in response to execution by one or more computing devices, cause operations including:

retrieving a data object; and

attaching key information to the data object via serialization, wherein the key information facilitates preserving relationships associated with the data object, and wherein a retrieval of a relationship varies according to whether a value included in the key information is null or non-null.

12. The hardware storage device of claim 11, wherein the operations further include associating the key information with a customer class.

13. The hardware storage device of claim 11, wherein the operations further include transporting the key information as a proxy for the data object during the serialization.

14. The hardware storage device of claim 13, wherein the operations further include attaching the data object to a tracking context.

15. The hardware storage device of claim 14, wherein the tracking context facilitates replacing the proxy with the data object in a graph.

16. A computer implemented system comprising at least one processor and at least one hardware storage device having stored thereon instructions executable by the at least one processor to:

retrieve a data object; and

attach key information to the data object via serialization, wherein the key information facilitates preserving relationships associated with the data object, and wherein a retrieval of a relationship varies according to whether a value included in the key information is null or non-null.

17. The computer-implemented system of claim 16, wherein the instructions are also executable by the at least one processor to retrieve the at least one of the plurality of relationships from a state manager when the value is non-null.

18. The computer-implemented system of claim 16, wherein the instructions are also executable by the at least one processor to retrieve the at least one of the plurality of relationships from a source data object when the value is null.

19. The computer-implemented system of claim 16, wherein the instructions are also executable by the at least one processor to retrieve the at least one of the plurality of relationships from a private field when the data object is detached.

20. The computer-implemented system of claim 19, wherein the at least one of the plurality of relationships included in the private field is set during serialization.