CN102662995A - Method for quickly positioning data updating of mobile phone applications - Google Patents

Abstract

A method for rapidly locating mobile phone application data updates, comprising the following steps: selecting a monitoring data table and a field to be monitored, creating a base table, and determining the data table in which data updates occur; the state of the updated data table and the base table records Compare the data status of the data to determine the record of the data update; record the record of the above data update to the database. By adopting the method of the invention, data update can be monitored in real time, the updated data can be determined, and required applications can be notified.

Description

A method for quickly locating mobile phone application data updates

technical field

The invention relates to the technical field of databases, in particular to a positioning method for updating data of a database.

Background technique

In the prior art, the means for discovering the update of the application data of the smart phone mainly include: the observer mode (android Observer) and the Trigger mechanism of the application database table.

The observer mode is also called the publish-subscribe (Publish/Subscribe) mode, the model-view (Model/View) mode, the source-listener (Source/Listener) mode or the slave (Dependents) mode. The Observer pattern defines a one-to-many dependency, allowing multiple observer objects to monitor a subject object at the same time. When the subject object changes in state, it notifies all observer objects, enabling them to automatically update themselves.

Apply the Trigger mechanism of the database table, which is closely connected with the table, built based on the table, and can be regarded as a part of the table. It cannot be called explicitly. After the user creates a trigger, when the data in the table is inserted, deleted or modified, the trigger will run automatically. The Trigger mechanism enables multiple different users to perform modification operations in a good environment that maintains data integrity and consistency.

The observer mode mentioned above can only monitor the table level, that is to say, only which table has changed can be determined through Observer, and which record has changed cannot be located. When the Trigger mechanism detects the change of the record, it triggers the processing SQL operation, and the change of the data record skips the application processing program, so that the user cannot further process the change of the application record.

Contents of the invention

In order to solve the deficiencies in the prior art, the purpose of the present invention is to provide a method for quickly locating mobile phone application data updates. For the data table to be monitored, first create a base table to record the state before the data update, and then use the observer mode (Android Observer) When data is updated, determine the data update data table, compare the state of the updated data table with the data state of the base table record, find out the inconsistent records, and determine the data update record.

In order to achieve the above object, a method for fast data classification provided by the present invention comprises the following steps:

1) Select the data table to be monitored and the field to be monitored, create a base table, and then use the observer mode to determine the occurrence of data to update the data table when the data is updated;

2) Compare the status of the updated data table with the data status of the base table records, find out the inconsistent records, and determine the data update records;

3) Record the record of the above data update to the database.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention.

Description of drawings

The accompanying drawings are used to provide a further understanding of the present invention, and constitute a part of the specification, and together with the contents and embodiments of the present invention, are used to explain the present invention, and do not constitute a limitation to the present invention. In the attached picture:

FIG. 1 is a flow chart of a method for quickly locating mobile phone application data update according to the present invention.

Detailed ways

Preferred embodiments of the present invention will be described below in conjunction with the accompanying drawings. It should be understood that the embodiments described here are only used to illustrate and explain the present invention, and are not intended to limit the present invention.

The method of the present invention records the initial state of the data table to be monitored, and monitors the application data based on the observer mode (android Observer). When the data changes, it can be determined which data table of which application has changed; then, compare the changes After the state of the data table and the initial state, find out the changes and determine which record has changed.

Fig. 1 is a flow chart of the method for updating the application data of the fast positioning mobile phone according to the present invention, and with reference to Fig. 1, the method for updating the application data of the fast positioning mobile phone of the present invention is described in detail:

First, in step 101, select the data table where the application data to be monitored and the field to be monitored are selected, and a field that can indicate whether the field to be monitored is changed is found. Concatenate the field values that can indicate whether the monitoring data has changed into a string, and calculate the hash value of the string. Based on these hash values, record the initial state of the monitoring data table and create a base table; the main fields of the base table include : "_id" (identification of the monitoring data table), "state_value" (state value), "uri" (indicating the monitoring data table), "recordId" (corresponding _id in the monitoring data table). The status value is the hash value calculated according to the monitoring field of the monitoring data table. The data table and fields to be monitored here are selected according to the needs of the user, and the initial state is recorded by scanning the monitored data table;

In step 102, when the android Observer detects the data update, it determines the data table for the data update according to the "uri", compares the initial state of the base table, and finds out the specific record of the data change.

The method of comparing the two tables is: first, use "uri" to fetch data D1 from the base table in descending order of "recordId", and use uri to fetch data D2 from the updated data table in descending order of "_id". Then, take D1 and D2 records in turn for comparison.

a) If the "recordId" of D1 is greater than the "_id" of D2, it means that the record with "_id" equal to "recordId" in the monitoring data table corresponding to D2 has been deleted. Take the next record in D1, keep the record in D2 unchanged, and perform the next comparison. As shown in Table 1, recordId > _id, delete _id = 6.

Table 1: Data removal

(D1) recordId (D2)_id 9 9 8 8 6 the 5 5 4 4

b) If the "recordId" of D1 is smaller than the "_id" of D2, it means that the record in the monitoring data table corresponding to D2 is a newly added record. Take the next record in D2, keep the record in D1 unchanged, and perform the next comparison. As shown in Table 2, recordId < _id , add _id=9.

Table 2: Data addition

(D1) recordId (D2)_id the 9 8 8 6 6 5 5 4 4

c) If the "recordId" of D1 is equal to the "_id" of D2, calculate the hash value corresponding to the monitored field of the monitored data table, and compare it with the corresponding "state_value" in the base table. If the two values are the same, it means The data is not updated. If it is different, it means that the record in the monitoring data table corresponding to D2 has been updated. Take the next record of D1 and D2 for the next comparison. As shown in Table 3, when the corresponding hash values are different, there is data update.

Table 3: Data update

(D1) recordId (D2)_id 9 9 8 8 6 6 5 5 4 4

d) If there are no records in D1 and there are records in D2, it means that these records in D2 are newly added. As shown in Table 4, there are no records in D1, and there are records in D2, and the corresponding data in the monitoring data table are newly added.

Table 4:

(D1) recordId (D2)_id the 5 the 4 the 3 the 2 the 1

e) If there are no records in D2 and there are records in D1, it means that the records with "_id" equal to "recordId" in D2 are deleted. As shown in Table 5, there are no records in D2, and there are records in D1, and the corresponding data in the monitoring data table are all deleted.

table 5:

(D1) recordId (D2)_id 9 the 8 the 6 the 5 the 4 the

In step 103, records of the above changes are recorded in the database for use by other applications.

At present, on the smart phone, there are many applications that are very concerned about the changes of some data of other applications, and hope to obtain the change information of these applications. For example, mobile phone dialing needs to know the changes of the address book data in order to dial through the address book. It needs to know the changes of short messages and know which contacts have more contacts, so that users can find these contacts most easily. Another example is search, which needs to know the changes in the data of each application, so that users can search for existing information and not find information that does not exist, and so on. However, the current means of discovering other application changes is far from enough. Using the method for quickly locating mobile phone application data updates of the present invention can monitor data updates in real time, determine updated data, and notify required applications.

Those of ordinary skill in the art can understand that: the above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, for those skilled in the art, It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (5)

1. A method for quickly locating mobile phone application data updates, comprising the following steps: 1) Select the monitoring data table and the monitoring field, create the base table, and determine the data table where the data update occurs; 2) Compare the state of the updated data table with the data state recorded in the base table to determine the record for data update; 3) Record the record of the above data update to the database. 2. The method for quickly locating mobile phone application data updates according to claim 1, wherein the fields selected for detection in step 1) include: monitoring data table identifier "_id"; state value "state_value", indicating monitoring The data table "uri" and the corresponding _id "recordId" in the monitoring data table. 3. The method for quickly locating mobile phone application data updates according to claim 1, characterized in that the data table for which data updates are determined to occur in step 1) is monitored according to needs when data updates are detected using the observer mode The identifier of the data table, which determines the data table for data update. 4. The method for quickly locating mobile phone application data updates according to claim 2, wherein the state value "state_value" is a hash value calculated according to the monitoring field of the monitoring data table. 5. The method for quickly locating mobile phone application data updates according to claim 1, characterized in that the step 2) is to use "uri" to obtain data from the base table in descending order of "recordId" and use "uri" The data fetched from the updated data table in descending order of "_id" are compared in turn.

Images