Persistent query system for automatic on-demand data subscriptions from mobile devices

• US 7,752,165 B2
• Filed: 08/01/2007
• Issued: 07/06/2010
• Est. Priority Date: 08/01/2007
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Leckie, Kyle, Ireland, Evan, Clegg, David
• Primary Examiner(s): Corrielus; Jean M
• Application Number:
  US11/882,447
• Publication Number:
  US 20090037395A1
• Time in Patent Office: 1,070 Days
• Field of Search: 707/3, 707/10, 707/104.1, 707/609, 707/610, 707/617, 707/618, 707/619, 707/620, 707/621, 707/626, 707/628, 707/632
• US Class Current: 707/609
• 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

Abstract

A system, method, and computer program product are provided for creating a data subscription to a remote database. Additionally, a system, method, and computer program product are provided for creating a persistent query, wherein a table in a remote database is represented by a meta-data definition.

Claims

1. A method for creating a data subscription to a remote database, comprising:

marking a query to be performed on a table located within the remote database as persistent within a meta-data definition of the query, indicating that results for the query are persisted to a local database;

generating, in a processor, a persistent query entity based on the meta-data definition, wherein the persistent query entity is mapped to a persistent query table in the local database, each row of the persistent query table representing an invocation of the query with a particular set of parameters;

uploading the persistent query table to the remote database to create a subscription for the query corresponding to the particular set of parameters; and

generating query execution code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database.

2. The method of claim 1, wherein the query is implicitly defined by the meta-data definition.

3. The method of claim 1, wherein the query is explicitly defined by the meta-data definition.

4. The method of claim 1, wherein uploading the persistent query table comprises:

generating an upload cursor to upload the persistent query table to the remote database.

5. The method of claim 1, further comprising:

generating a download cursor.

6. The method of claim 5, wherein the step of generating a download cursor comprises:

generating a query, the query operable to obtain entries from the table that correspond to entries in the persistent query table.

7. The method of claim 1, further comprising:

distributing a row from the persistent query table to a second local database.

8. The method of claim 1, further comprising:

mapping a second persistent query entity to the persistent query table responsive to the mapping of the persistent query entity to the persistent query table.

9. The method of claim 8, wherein the mapping of the second persistent query entity is performed if an application issuing the query requires use of the second persistent query entity.

10. A computer-readable storage medium having instructions stored thereon that, when executed by a computing device, cause a processor to perform a method for creating a data subscription to a remote database, the method comprising:

marking a query to be performed on a table located within the remote database as persistent within a meta-data definition of the query, indicating that results for the query are persisted to a local database;

generating a persistent query entity based on the meta-data definition, wherein the persistent query entity is mapped to a persistent query table in the local database, each row of the persistent query table representing an invocation of the query with a particular set of parameters;

uploading the persistent query table to the remote database to create a subscription for the query corresponding to the particular set of parameters; and

generating query execution code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database.

11. A system capable of creating a data subscription to a remote database, comprising:

a memory configured to store;

a marking module configured to mark a query to be performed on a table located within the remote database as persistent within a meta-data definition of the query, indicating that results for the query are persisted to a local database;

a generating module configured to generate a persistent query entity based on the meta-data definition, wherein the persistent query entity is mapped to a persistent query table in the local database, each row of the persistent query table representing an invocation of the query with a particular set of parameters;

an uploading module configured to upload the persistent query table to the remote database to create a subscription for the query corresponding to the particular set of parameters; and

a generating module configured to generate query execution code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database; and

 

one or more processors configured to process the modules.

12. A computer-implemented method for creating a persistent query, wherein a table in a remote database is represented by a meta-data definition, comprising:

identifying, in the definition, a query to be performed on the table, wherein the query has been marked as a subscribed query;

defining a persistent query entity for the subscribed query, indicating that results for the subscribed query are persisted to a local database;

mapping the persistent query entity to a persistent query table, each row of the persistent query table representing an invocation of the subscribed query with a particular set of parameters;

uploading the persistent query table to the remote database to create a subscription for the subscribed query corresponding to the particular set of parameters; and

generating query code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database.

13. The method of claim 12, further comprising:

generating an upload cursor to upload the persistent query table to the remote database.

14. The method of claim 12, further comprising:

receiving an instance of the subscribed query; and

consulting the persistent query table to determine if a result of the instance of the subscribed query is contained in the local database.

15. The method of claim 14, wherein the result of the instance of the subscribed query is contained in the local database, further comprising:

retrieving the result from a copy of the table in the local database.

16. The method of claim 14, further comprising:

synchronizing the local database with the remote database.

17. The method of claim 16, wherein the step of synchronizing the local database with the remote database comprises:

selecting rows from the remote database by joining the table with the persistent query table; and

downloading the selected rows to the local database.

18. The method of claim 17, wherein the set of selected rows consist of only rows modified or subscribed to since the last synchronization.

19. The method of claim 17, wherein the steps of selecting rows and downloading the selected rows are implemented in a download cursor.

20. The method of claim 17, wherein the step of downloading the selected rows to the local database creates a copy of the table in the local database.

21. The method of claim 14, wherein the result of the instance of the subscribed query is not contained in the local database, further comprising:

creating an entry in the persistent query table corresponding to the instance of the subscribed query.

22. The method of claim 12, further comprising:

distributing a row from the persistent query table to a second local database.

23. The method of claim 12, further comprising:

mapping a second persistent query entity to the persistent query table responsive to the mapping of the persistent query entity to the persistent query table.

24. The method of claim 23, wherein the mapping of the second persistent query entity is performed if an application issuing the query requires use of the second persistent query entity.

25. A computer-readable storage medium having instructions stored thereon that, when executed by a computing device, cause a processor to perform a method for creating a persistent query, wherein a table in a remote database is represented by a meta-data definition, the method comprising:

identifying, in the definition, a query to be performed on the table, wherein the query has been marked as a subscribed query;

defining a persistent query entity for the subscribed query, indicating that results for the subscribed query are persisted to a local database;

mapping the persistent query entity to a persistent query table, each row of the persistent query table representing an invocation of the subscribed query with a particular set of parameters;

uploading the persistent query table to the remote database to create a subscription for the subscribed query corresponding to the particular set of parameters; and

generating query code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database.

26. A system capable of creating a persistent query, wherein a table in a remote database is represented by a meta-data definition, comprising:

a memory configured to store;

an identifying module configured to identify, in the definition, a query to be performed on the table, wherein the query has been marked as a subscribed query;

a defining module configured to define a persistent query entity for the subscribed query, indicating that results for the subscribed query are persisted to a local database;

a mapping module configured to map the persistent query entity to a persistent query table, each row of the persistent query table representing an invocation of the subscribed query with a particular set of parameters;

an uploading module configured to upload the persistent query table to the remote database to create a subscription for the subscribed query corresponding to the particular set of parameters; and

a generating module configured to generate query code to;

consult the persistent query table to determine if the result of an instance of the persistent query is contained in the local database,

consult the local database if the result of the instance of the persistent query is contained in the local database, and

create an entry in the persistent query table if the result of the instance of the persistent query is not contained in the local database; and

one or more processors configured to process the modules.