View maintenance rules for an update pipeline of an object-relational mapping (ORM) platform

• US 20080228697A1
• Filed: 03/16/2007
• Published: 09/18/2008
• Est. Priority Date: 03/16/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Adya, Atul, Meek, Colin Joseph, Melnik, Sergey, Michailov, Zlatko
• Granted Patent: US 9,430,552 B2
• Time in Patent Office: Days
• US Class Current: 707/2
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A database update pipeline may be incorporated into a data access architecture for providing data services to applications, thereby bridging the gap between application data and data as persisted in databases. The update pipeline has the ability to translate changes made to object instances into data store change constructs, and carry those changes over to a data store. Such a pipeline can also advantageously perform the reverse operation, allowing applications to query using the database update pipeline, and receive materialized object instances.

Claims

1. A method for providing data services to an application, comprising:

receiving, by a data access system, application data modifications, wherein said application data modifications are expressed according to an application schema;

utilizing incremental view maintenance to translate said application data modifications into relational database modifications expressed according to a database schema, wherein said utilizing incremental view maintenance includes;

applying at least one view maintenance rule that specifies a view operator, and given said application data modifications, produces said relational database modifications.

2. The method of claim 1, wherein said receiving, by a data access system, application data modifications comprises extracting said application data from a client computer cache.

3. The method of claim 1, further comprising updating a relational database with said relational database modifications.

4. The method of claim 1, wherein said at least one view maintenance rule is also given pre-existing data.

5. The method of claim 1, wherein said at least one view maintenance rule comprises an insert rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi-join rule.

6. The method of claim 1, wherein said at least one view maintenance rule comprises a delete rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi-join rule.

7. The method of claim 1, further comprising selecting an optimization level.

8. The method of claim 7, wherein said applying at least one view maintenance rule comprises applying a version of said view maintenance rule corresponding to said optimization level.

9. The method of claim 7, wherein said selecting an optimization level comprises selecting from among a plurality of optimization levels, said optimization levels requiring differing application data or relational database data when utilizing said incremental view maintenance

10. The method of claim 9, wherein said plurality of optimization levels comprise:

a traditional view maintenance level;

an insert/delete/update compatible level;

an insert/delete compatible level; and

a modification requests only level.

11. A data access system for providing data services to an application, comprising:

a subsystem for receiving, by a data access system, application data modifications, wherein said application data modifications are expressed according to an application schema;

a subsystem for utilizing incremental view maintenance to translate said application data modifications into relational database modifications expressed according to a database schema, wherein said a subsystem for utilizing incremental view maintenance includes;

a subsystem for applying at least one view maintenance rule that specifies a view operator, and given said application data modifications, produces said relational database modifications.

12. The system of claim 11, wherein said subsystem for receiving, by a data access system, application data modifications comprises a subsystem for extracting said application data from a client computer cache.

13. The system of claim 11, further comprising a subsystem for updating a relational database with said relational database modifications.

14. The system of claim 11, wherein said subsystem for applying at least one view maintenance rule is also given pre-existing data.

15. The system of claim 11, wherein said at least one view maintenance rule comprises an insert rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi join rule.

16. The system of claim 11, wherein said at least one view maintenance rule comprises a delete rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi-join rule.

17. The system of claim 11, further comprising a subsystem for selecting an optimization level.

18. The system of claim 17, wherein said subsystem for applying at least one view maintenance rule comprises a subsystem for applying a version of said view maintenance rule corresponding to said optimization level.

19. The system of claim 17, wherein said subsystem for selecting an optimization level selects from among a plurality of optimization levels, said optimization levels requiring differing application data or relational database data when utilizing said incremental view maintenance

20. The system of claim 19, wherein said plurality of optimization levels comprise:

a traditional view maintenance level;

an insert/delete/update compatible level;

an insert/delete compatible level; and

a modification requests only level.

21. A computer readable medium bearing instructions for providing data services to an application, said instructions comprising:

instructions for receiving, by a data access system, application data modifications, wherein said application data modifications are expressed according to an application schema;

instructions for utilizing incremental view maintenance to translate said application data modifications into relational database modifications expressed according to a database schema, wherein said instructions for utilizing incremental view maintenance include;

instructions for applying at least one view maintenance rule that specifies a view operator, and given said application data modifications, produces said relational database modifications.

22. The computer readable medium of claim 21, wherein said instructions for receiving, by a data access system, application data modifications comprises instructions for extracting said application data from a client computer cache.

23. The computer readable medium of claim 21, further comprising instructions for updating a relational database with said relational database modifications.

24. The computer readable medium of claim 21, wherein said instructions for applying at least one view maintenance rule are also given pre-existing data.

25. The computer readable of claim 21, wherein said at least one view maintenance rule comprises an insert rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi-join rule.

26. The computer readable of claim 21, wherein said at least one view maintenance rule comprises a delete rule selected from a group comprising a selection rule, a projection rule, a join rule, a union rule, and a semi-join rule.

27. The computer readable medium of claim 21, further comprising instructions for selecting an optimization level.

28. The computer readable medium of claim 27, wherein said instructions for applying at least one view maintenance rule comprise instructions for applying a version of said view maintenance rule corresponding to said optimization level.

29. The computer readable medium of claim 27, wherein said instructions for selecting an optimization level select from among a plurality of optimization levels, said optimization levels requiring differing application data or relational database data when utilizing said incremental view maintenance

30. The computer readable medium of claim 29, wherein said plurality of optimization levels comprise:

a traditional view maintenance level;

an insert/delete/update compatible level;

an insert/delete compatible level; and

a modification requests only level.