Rich application view system and method

• US 20060004794A1
• Filed: 06/30/2004
• Published: 01/05/2006
• Est. Priority Date: 06/30/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Klein, Johannes, Pizzo, Michael J., Fang, Lijiang, Li, Jian
• Application Number:
  US10/882,061
• Publication Number:
  US 20060004794A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2445 Data retrieval commands; View definitions
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/24552 Database cache management

Abstract

The present invention relates to systems and methods to provide rich interaction with persisted data. In particular, an application view is generated for each application and dynamically maintained to provide a rich experience working with data, including but not limited to an ability to scroll through large sets of data while viewing additions, deletions, and other changes made to the underlying data in real-time. According to one aspect of the invention, the application view is generated from a view table that includes aggregates and fully expanded groups at each level and a second table that comprises the expanded/collapsed state of grouped rows.

Claims

1. A system to support rich application interaction with stored data comprising:

an application view created for use by an application; and

a maintenance component for dynamically updating the view as changes are made to corresponding data in a database, wherein the view facilitates rich interaction with persisted data.

2. The system of claim 1, wherein the view is a temporary table.

3. The system of claim 1, wherein the maintenance component polls the database periodically to determine if the view needs to be updated.

4. The system of claim 1, wherein the database monitors view data and notifies the maintenance component of changes thereto.

5. The system of claim 4, wherein the maintenance component applies the changes to the view.

6. The system of claim 4, wherein the database employs a standing wait for query to monitor data.

7. The system of claim 4, wherein the database utilizes one of a trigger, notification, and polling to detect and indicate the occurrence of a change.

8. The system of claim 1, wherein the maintenance component notifies the application when a change is made to the application view.

9. The system of claim 1, wherein the view is shared by multiple consumers.

10. The system of claim 1, further comprising a view table and a state table to facilitate generation of the view, the state table housing view filtration data.

11. The system of claim 10, wherein the filtration data concerns data groups that can be expanded or collapsed.

12. The system of claim 11, wherein scrolling initiates a join operation between the view table and the state table producing a view that fills a user window.

13. The system of claim 10, wherein multiple state tables are used by different consumers of the same view table.

14. The system of claim 1, wherein the application view caches keys to base table rows and data necessary to sort view tuples in the required order.

15. The system of claim 1, wherein the application creates shared indexes to extract pre-sorted application view data to facilitate the creation of application views for multiple users.

16. The system of claim 1, wherein the application is an electronic mail application.

17. A persistent data interaction system comprising:

a means for generating a unique application view for each application instance that interacts with a database; and

a means for dynamically synchronizing the view with the database.

18. The system of claim 17, wherein the view is a temporary table.

19. The system of claim 17, wherein the view is a dynamically generated at least in part from a view definition upon query execution.

20. The system of claim 17, wherein the view is synchronized by database standing queries.

21. The system of claim 17, wherein the view is synchronized utilizing database triggers.

22. The system of claim 17, wherein the view is synchronized utilizing database polling.

23. The system of claim 17, wherein the view is synchronized employing query notifications.

24. A method of data interaction comprising:

querying an application view associated with an particular application instance; and

receiving results.

25. The method of claim 24, wherein the results are grouped such that portions of the results are expanded and others are collapsed.

26. The method of claim 25, wherein the application view is populated by joining a view table and a state table, the state table containing data designating expanded and collapsed data units.

27. The method of claim 26, wherein the view table is sorted utilizing a clustered index to facilitate expeditious update thereto.

28. The method of claim 24, where the application view is generated dynamically from a query definition upon execution of a query.

29. The method of claim 28, wherein the query definition is stored on a client machine and transferred to a server for query execution.

30. The method of claim 24, further comprising the caching a set of results from the application view.

31. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 24.

32. A method of supporting rich client application interactions with databases comprising:

generating an application view for each application session; and

dynamically maintaining the view such that each view and associated database data are synchronized.

33. The method of claim 32, wherein the generation of the application view comprises producing a view table that houses a subset of database data.

34. The method of claim 33, further comprising executing standing queries to synchronize data.

35. The method of claim 34, further comprising creating a state table to indicate an expand/collapse state associated with each data unit.

36. The method of claim 32, further comprising executing queries on the application view to retrieve a range of data to fill a user view.

37. The method of claim 36, wherein executing a query comprises joining a view table comprising a fully expanded set of data and a state table specifying data unit expand/collapse states.

38. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 32.