Entity triggers for materialized view maintenance

Abstract

A system, method, and computer program product are provided for implementing materialized views on a mobile device in synchronization with an enterprise information system. Changes to an underlying local database, on which the materialized view is based, may originate from the enterprise system or from the client. A solution needs to account for each of these potential sources of changes, and update the materialized view accordingly.

1 . A method comprising:
 defining a mobile business object for a materialized view;   defining triggers, within the mobile business object, for changes to a local database affecting the materialized view; and   executing a code generator on the mobile business object definition.   
     
     
         2 . The method of  claim 1 , wherein the changes to the local database comprise at least one of a create, update, or delete call. 
     
     
         3 . The method of  claim 1 , wherein the changes to the local database comprise a bulk initial download. 
     
     
         4 . The method of  claim 1 , further comprising:
 writing platform-specific code for the triggers to maintain the materialized view.   
     
     
         5 . The method of  claim 1 , wherein the changes to the local database comprise a download, and wherein defining triggers comprises defining a trigger activated upon saving the download to the local database. 
     
     
         6 . The method of  claim 1 , wherein defining triggers comprises defining a trigger for a delete call configured to not fail if a source MBO for the delete call is not present. 
     
     
         7 . A computer-readable storage device having computer program logic recorded thereon, execution of which, by a computing device, causes the computing device to perform operations comprising:
 defining a mobile business object for a materialized view;   defining triggers, within the mobile business object, for changes to a local database affecting the materialized view; and   executing a code generator on the mobile business object definition.   
     
     
         8 . The computer-readable storage device of  claim 7 , wherein the changes to the local database comprise at least one of a create, update, or delete call. 
     
     
         9 . The computer-readable storage device of  claim 7 , wherein the changes to the local database comprise a bulk initial download. 
     
     
         10 . The computer-readable storage device of  claim 7 , the operations further comprising:
 writing platform-specific code for the triggers to maintain the materialized view.   
     
     
         11 . The computer-readable storage device of  claim 7 , wherein the changes to the local database comprise a download, and wherein defining triggers comprises defining a trigger activated upon saving the download to the local database. 
     
     
         12 . The computer-readable storage device of  claim 7 , wherein defining triggers comprises defining a trigger for a delete call configured to not fail if a source MBO for the delete call is not present. 
     
     
         13 . A system comprising:
 a memory configured to store modules comprising:
 a first defining module configured to define a mobile business object for a materialized view, 
 a second defining module configured to define triggers, within the mobile business object, for changes to a local database affecting the materialized view, and 
 an executing module configured to execute a code generator on the mobile business object definition; and 
   one or more processors configured to process the modules.   
     
     
         14 . The system of  claim 13 , wherein the changes to the local database comprise at least one of a create, update, or delete call. 
     
     
         15 . The system of  claim 13 , wherein the changes to the local database comprise a bulk initial download. 
     
     
         16 . The system of  claim 13 , further comprising:
 a writing module configured to write platform-specific code for the triggers to maintain the materialized view.   
     
     
         17 . The system of  claim 13 , wherein the changes to the local database comprise a download, and wherein defining triggers comprises defining a trigger activated upon saving the download to the local database. 
     
     
         18 . The system of  claim 13 , wherein defining triggers comprises defining a trigger for a delete call configured to not fail if a source MBO for the delete call is not present.