JPH09128280A - Data management device and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten a synchronizing process time and to optimize a way of synchronization by providing a means which regards only data which have variation from last synchronization as objects to be synchronized and then shortens the time of the synchronizing process and a means which optimizes the way of synchronizing originally identical data. SOLUTION: A CPU 11 has variation states of data in a data base 14 from last synchronization by the data by referring to a synchronizing program 13 in a storage device 12. Then when the data base is synchronized as to only data having variation from the last synchronization by performing synchronization with a data base having variation state information on other equipment of the same equipment constitution, it is judged from the variation state of the data whether data needs to be synchronized, and only object data are synchronized.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a synchronous process for reflecting the change state of data in databases on a plurality of devices, particularly two devices, in both databases to make the data in the databases identical. The present invention relates to a data management device and a data management method provided with.

[0002]

2. Description of the Related Art Conventionally, when synchronizing a database, for example, all data is communicated between devices regardless of whether or not there is a change, and is targeted for synchronization. Also, when the same data is originally modified separately on both devices, the modified data is unconditionally added to the other database.

The term "synchronization" here refers to databases on two devices. The databases on these two devices are originally the same data, but by being used separately by the two devices, one can add /
Corrected / deleted data and added / corrected / on the other device
The deleted data will exist separately in both databases. In such a case, the data added / corrected / deleted by one device is mutually reflected in the database on the other device to make both databases the same.

[0004]

As described above, in the conventional method, even if there is no change in the data from the previous synchronization, all the data are communicated between the devices and are subject to the synchronization. There was a problem that it took time.

Further, when the same data is originally corrected separately on both devices, even if the correction contents are the same, they are mutually added to the other database. For this reason, there is a problem that the data having the same content becomes two and wasteful data increases, resulting in waste of memory capacity.

The present invention has been made in consideration of the above circumstances, and a means for shortening the synchronization processing time by making only the data that has changed from the previous synchronization the object of synchronization, and both. A data management device and a data management method, which are provided with means for optimizing the synchronization of originally identical data corrected in a database, and which enable shortening of the synchronization processing time and optimization of the synchronization. The purpose is to provide.

[0007]

SUMMARY OF THE INVENTION In order to achieve the above object, the present invention provides a device for managing a database with an electronic notebook, a personal computer or the like, in which the same database existing on a plurality of devices is used. When the databases become different data by being used separately by the device, the synchronization means for making the data in the databases the same and the change state of the data after the synchronization performed last time for each data in the database In the case of synchronizing the databases on the plurality of devices by including means as information, based on the change state information by the means, only the data that has changed after the previous synchronization is targeted, The data management device is characterized in that the missing data is excluded from the synchronization target so that the synchronization can be performed at high speed.

In order to achieve the above object, the present invention is, in the above-mentioned data management device, a judging means for judging the correction degree of each data when the data to be synchronized is corrected in each database. If each data has the same contents but the details are modified differently, the data with more detailed contents is considered as valid data, this valid data is added to other database, and the remaining The data that is not familiar with is deleted from the database.

Further, in order to achieve the above object, the present invention provides
In the above data management device, when the data to be synchronized is modified in each database, a judgment is made as to whether or not the contents of each data are different in expression but the contents are similarly modified. Means is provided so that when it is determined that each data has a different expression but the content is modified to the same, each data is not synchronized and is left as it is in each database.

Further, in order to achieve the above object, the present invention provides
In the above data management device, when the data to be synchronized is modified in each database, a judgment means is provided to judge whether each data is modified with different contents, and each data is different. When it is determined that the contents have been corrected, the correction data of one is added to the database of the other, and the original correction data is left without being deleted.

Further, in order to achieve the above object, the present invention provides:
In the case of a device that manages a database with an electronic organizer, a personal computer, etc., when the same database that exists on multiple devices is used separately for each device and the database becomes different data , The data in the database is made the same, and control is performed so that each data in the database has the change state of the data after the previous synchronization, and when the databases in the plurality of devices are synchronized, the change state information Based on the above, there is a data management method characterized in that only the data that has changed after the previous synchronization is targeted, and the data that has not changed is excluded from the target of synchronization so that the synchronization is performed at high speed. .

According to the above-mentioned configuration, since only the data that has changed from the previous synchronization is targeted for synchronization, useless data communication and synchronization processing can be omitted and the synchronization processing time can be shortened. You can

Further, when the same data is modified in both databases, the case where the details are different but the contents are the same, the case where the expressions are different but the contents are the same, and the case where the contents are different. By determining the three patterns, it is possible to optimize the originally same data that has been modified in both databases and prevent the useless increase of data.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The outline of the present invention is as follows. That is, the means for holding the change state of the data from the previous synchronization as information for each data in the database, and the means for synchronizing with the database having the change state information on another device of the same device configuration, By providing a means to target only the data that has changed from
When synchronizing the databases, it is determined whether or not the data is to be synchronized based on the change state of the data, and only the data to be synchronized is synchronized. Further, means for synchronizing the above, means for judging whether the contents of the two data are different in detail but the contents are the same, and means for judging whether contents of the two data are different in expression but the contents are the same. By providing a means for judging whether or not the contents of the two data are different, the method of synchronizing the originally same data corrected in both databases is optimized.

In summary, the present invention is: (1) In a device that manages a database with an electronic notebook, a personal computer or the like, the same database existing on a plurality of devices is used separately for each device. When the database becomes different data, the synchronization means for making the data of the database the same, a means for holding as information the change state of the data after the previous synchronization for each data of the database, When synchronizing the databases on the plurality of devices, based on the change state information by the means, only the data that has changed after the previous synchronization is targeted, and the data that has not changed is excluded from the synchronization target. As a result, the data management device can perform synchronization at high speed.

(2) In the above data management device,
When the data to be synchronized is modified in each database, a judgment means is provided to judge the extent of modification of each data, and when each data has the same content but different details are modified. , I made the data with more detailed contents valid data, added this valid data to another database, and deleted the remaining undetailed data from the database.

(3) In the above data management device,
When the data to be synchronized is modified in each database, the content of each data is different in expression, but there is a judgment means to judge whether the content is modified in the same way, and each data is expressed. When it is determined that the contents are modified to be the same although different, the data is not synchronized and is left as it is in each database.

(4) Further, in the above-mentioned data management device, when the data to be synchronized is modified in each database, a judging means for judging whether each data is modified with different contents is provided. When it is determined that each data has been modified with different contents, one of the modified data is added to the other database, and the original modified data is left without being deleted.

According to the above-mentioned configuration, since only the data that has changed since the previous synchronization is targeted for synchronization, useless data communication and synchronization processing can be omitted, and the synchronization processing time can be shortened. You can In addition, when the same data is modified in both databases, there are three types of cases: different details but the same content, different expressions but the same content, and different contents. By determining the pattern, it is possible to optimize the originally synchronized data that has been modified in both databases, and prevent an unnecessary increase in data.

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the basic configuration of a document creating apparatus according to an embodiment of the present invention.

Reference numeral 11 denotes a microprocessor (CPU), which controls the entire apparatus. Here, various processing controls relating to database synchronization as shown in FIGS. 3 to 5 are executed.

A storage device 12 stores programs, dictionaries, other various data, and the like. Here, a database, a synchronization program, and the like that are the objects of synchronization control are stored.

Reference numeral 13 is a synchronization program stored in the storage device 12, and has a processing routine for synchronizing the database. A database 14 stored in the storage device 12 is a database (database X) for synchronization.

Reference numeral 15 denotes a communication interface (communication-I
F), which is a CP for an external device and a database stored in the storage device 12 by RS-232C or infrared rays.
It transmits and receives under the control of U11.

Reference numeral 17 denotes an input device, which uses the input interface (input IF) 16 to input data to the CPU 11 and activate synchronous processing. Reference numeral 19 denotes a display device, which uses a display dot memory 20 to display a database or the like stored in the storage device 12 using a display control device (display CN.
T) 18 and the display under the control of the CPU 11.

A printer (PRT) 22 prints a database or the like stored in the storage device 12 under the control of the printer interface (PRT-IF) 21 and the CPU 11.

Reference numeral 24 denotes a floppy disk drive (FD
D) is an external storage device such as a hard disk drive (HDD), and a database or the like stored in the storage device 12 is a disk interface (FDD / HDD-IF).
23, and save and call under the control of the CPU 11.

FIG. 2 is a conceptual diagram of a device having the same components as in FIG. In FIG. 2, reference numeral 25 is a device having the same components as in FIG. 1, and a database (database Y) 26 of the device 25 has a database X14 via the communication interface (communication-IF) 15 shown in FIG. Synchronize.

The synchronization here is intended for databases on two devices. The databases on these two devices are originally the same data,
When used separately on two devices, data added / modified / deleted on one device and data added / modified / deleted on the other device exist separately in both databases. . In such a case, the data added / corrected / deleted by one device is mutually reflected in the database on the other device to make both databases the same.

FIG. 3 is a flow chart in the embodiment of the present invention. In FIG. 3, step S1 is a step of sequentially extracting data to be synchronized from the database one by one.

Step S2 is a step of ending the synchronization when there is no target data for the synchronization in step S1. Step S3 is a step of checking whether the changed state of the data extracted in step S1 is addition.

Step S4 is a step of registering the data retrieved in step S1 in the other database if the result checked in step S3 is additional. Step S5 is a step of checking whether the changed state of the data taken out in step S1 is a correction.

Step S6 is a step for performing processing when the result checked in step S5 is a correction. Step S7 is a step of checking whether the changed state of the data extracted in step S1 is deletion.

Step S8 is a step for performing processing when the result checked in step S7 is deletion. FIG. 4 is a flowchart showing in detail the process of step S6 of FIG.

Step S11 is a step of extracting change state information of the same data as the data acquired in step S1 from the other database. Step S12
Is a step of checking whether or not the changed state extracted in step S11 is a correction.

In step S13, if the result checked in step S12 is a correction,
This is a step of extracting the same data as the data acquired in step S1.

Step S14 is a step for checking whether or not the correction contents of the data extracted in step S1 and the data extracted in step S13 are the same although the details are different.

In step S15, when it is determined that the result checked in step S14 is different in detail but the contents are the same, the more detailed data is registered in the other database, and the less detailed data is deleted from the database. It is a step.

Step S16 is a step of checking whether the correction contents of the data fetched in step S1 and the data fetched in step S13 have different expressions but the same contents.

Step S17 is a step of registering the data taken out in step S1 in the other database when it is determined that the results checked in step S16 are different in content.

Step S18 is a step of replacing the same data in the other database with the data fetched in step S1 if the result checked in step S12 is other than correction.

FIG. 5 is a flow chart showing in detail the process of step S8 of FIG. Step S21 is a step of extracting change state information of the same data as the data acquired in step S1 from the other database.
Step S22 is a step of checking whether or not the changed state extracted in step S21 is a correction.

Step S23 is a step of deleting data from both databases if the check result of step S22 is other than correction. FIG. 6 shows a state in which the database X and the database Y are synchronized and then changes are made to both databases.
These databases have the following features. Each data includes "change state" information indicating what kind of change has occurred since the previous synchronization. Further, conventionally, in the case of deletion, data is deleted from the database, but in the present invention, since the "change state" information for each data is held, all or part of the content of the deleted data is left.

FIG. 7 shows that the database X and the database Y of FIG. 6 are synchronized. Based on the “change state” information in the database, data that has not changed is excluded from synchronization, and only data that has changed is subject to synchronization.

FIG. 8 shows the state of the database after the synchronization. Database X and database Y
The synchronization is executed and the data is the same. Further, the "change state" information is all unchanged.

FIG. 9 shows a database X and a database Y.
In both cases, the details are different for the same data A, but the contents are shown to be in synchronization after the same correction.

The corrected data A'and data A "are different in detail but are the same up to the town name, so it is judged that they are the same data. , And data A'has been deleted.

In this example, the same data is used when the street name of the address data is the same, but the method of determining whether the correction contents are the same depends on the database and the type of data.

FIG. 10 shows that the database X and the database Y are synchronized after the same data A has different expressions but the same contents are modified.

The corrected data A'and data A "represent different addresses but represent the same address, so they are judged to be the same data, and both data are not synchronized and are left in the original database as they are.

In this example, the judgment of whether or not the data have the same contents is made by using the same expression ("Chome" and "-", "address" and "-", etc.) having the same meaning used to represent an address. However, the judgment method depends on the database and the type of data. For example, when the data is a telephone number, "(" and "-", ")" and "-" can be regarded as the same.

FIG. 11 shows that the database X and the database Y are in synchronization after the same data A is modified with different contents. Since the contents of the corrected data A ′ and the data A ″ are different, it is determined that they are different data, and the data A ′ is added to the database Y and the data A ″ is added to the database X.

Whether the contents are the same or not can be determined by referring to FIG. 9 and FIG.
Judgment is made based on whether or not the correction content of is checked.
The operation of the configuration of the above embodiment will be described below.

The synchronizing operation according to the present embodiment when there is a request for synchronizing the databases as shown in FIG. 6 will be described. In synchronization, data that has not changed is excluded from synchronization, and only data that has changed is subject to synchronization based on the “change state” information of the database (see FIG. 3).

The data A of both the database X and the database Y is unchanged from the previous synchronization. Step S
In the case of 1, the data that has not changed from the previous synchronization is not extracted, so the data A is not the target of synchronization (see circled number 1 in FIG. 7).

The data B'of the database X has been modified since the previous synchronization. The data B'is taken out from the step S1, is judged to be corrected data in the step S5, and the data B of the database Y is replaced with the data B'of the database X taken out in the step S1 in the step S18 of the process of the step S6 (FIG. 7). 2).

Data C in database X has been deleted from the previous synchronization. The data C is extracted in step S1 and is determined to be deleted data in step S7.
In step S23 of the process of step S8, the data C in both the database X and the database Y is deleted (see FIG. 7).
See circled number 3).

The data D'of the database Y has been modified since the previous synchronization. The data D'is extracted from step S1, and the data D of the database X is replaced with the data D'of the database Y extracted in step S1 in step S18 of the correction data and the determination step S6 in step S5 (circle in FIG. 7). See number 4.)

The data E of the database X has been added since the previous synchronization. The data E is extracted in step S1 and is determined to be additional data in step S3.
The data E of the database X retrieved in step S1 in step S4 is registered in the database Y (see circled numeral 5 in FIG. 7).

The data F of the database Y has been added since the last synchronization. The data F is fetched in step S1 and is determined to be additional data by the step S3, and the data F of the database Y fetched in step S1 is registered in the database X in step S4 (see circled numeral 6 in FIG. 7).

By these processes, the database X and the database Y are synchronized, and the data in the database X and the database Y become the same (see FIG. 8). In this way, each data has "change state" information, and based on this information, it is judged whether or not it is the synchronization target, and the data that is not the synchronization target (data that has not changed from the previous synchronization) is synchronized. It can be removed from processing. Further, since the amount of data communication between the devices is reduced, the execution time of the synchronization process can be shortened.

Next, the operation of the synchronization according to the present embodiment when the same data is corrected separately in the two databases will be described. Data A'and data A "in FIG.
Originally, the same data A has the same contents but is modified with different details.

The data A'of the database X retrieved in step S1 is processed in step S5 in step S5.
Proceed to 6. In step S6, the change state information of the data A ″ of the database Y is extracted in step S11, and the process proceeds to step S13 in step S12.

In step S13, the data A "in the database Y is retrieved, and in step S14 the data A" is retrieved.
It is checked whether the contents of'and the data A'are the same although the details are different.

In the example of FIG. 9, it is determined in step S14 that the contents are the same, and the process proceeds to step S15. Step S
In 15, the detailed data A ”is registered as the valid data, and the data A” is registered in the database X.
Will be deleted.

The data A'and the data A "in FIG. 10 are originally the same as the data A but have the same contents but are modified in different expressions. Steps S1 to S13 are shown in FIG. The operation is similar.

The data A ″ of the database Y retrieved in step S13 is the data A ′ obtained in step S16.
And the data A "are different in expression, but it is checked whether the contents are the same.

In the example of FIG. 10, the contents are judged to be the same in step S16, the two are not synchronized, and code step S6 is executed.
Is completed. Data A'and data A "in FIG.
Is the same data A that is originally modified with different contents. The operation from step S1 to step S13 is the same as that of FIG.

The data A ″ of the database Y retrieved in step S13 is stored in steps S14 and S15.
In the example of FIG. 11, since the correction content is different, neither check is performed and the process proceeds to step S17.

In step S17, the data A'taken out in step S1 is registered in the database Y. At this time, there are a method of registering the data A ″ in the database X in step S17 and a method of leaving it to the process when the data A ″ is retrieved in step S1.

According to the above-described embodiment, since only the data that has changed since the previous synchronization is targeted for synchronization, useless data communication and synchronization processing can be omitted, and the synchronization processing time can be shortened. Is something that can be done.

When the same data is corrected in both databases, the details are different but the contents are the same, or the expressions are different but the contents are the same.
By determining the three patterns when the contents are different, it is possible to optimize the synchronization method and prevent unnecessary data increase. It should be noted that the present invention is not limited to the above embodiment, and it is of course possible to synchronize databases in the same device.

[0073]

As described above in detail, according to the present invention,
By subjecting only the data that has changed from the previous synchronization to the synchronization target, useless data communication and synchronization processing can be omitted, and the synchronization processing time can be shortened.
In addition, when the same data is modified in both databases, there are three patterns of different details but the same content, different expressions but the same content, and different content. By determining the above, it is possible to optimize the method of synchronization and prevent an unnecessary increase of data, and so on.

That is, according to the present invention, when the databases on a plurality of devices are synchronized, based on the change state information by the means, only the data that has changed after the previous synchronization is targeted and the change is made. By removing the data that does not exist from the synchronization target, unnecessary data communication and synchronization processing can be omitted, and the synchronization processing time can be shortened.

Further, according to the present invention, when the data to be synchronized is corrected in each database, a judging means for judging the degree of correction of each data is provided, and each data has the same content. If the details are modified differently, make sure that the more detailed data is valid data, add this valid data to another database, and delete the remaining less detailed data from the database. By doing so, it is possible to optimize the synchronization method and prevent an unnecessary increase in data.

Further, according to the present invention, when the data to be synchronized is modified in each database, whether the contents of each data are different in expression but the contents are similarly modified or not. If a judgment means is provided to judge that each data has a different expression but the content is modified to the same, the data is not synchronized and is left in each database as it is. It is possible to optimize the way of taking and prevent the increase of useless data.

Further, according to the present invention, when the data to be synchronized is modified in each database, a judging means for judging whether or not each data is modified with different contents is provided, and each judging means is provided. If it is determined that the data has been modified with different contents, one modification data is added to the other database mutually, and the original modification data is not deleted, but the synchronization method is optimized. It is possible to prevent the increase of unnecessary data.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a basic configuration of a document creation device according to an embodiment of the present invention.

FIG. 2 is a conceptual diagram of a device having the same components as in FIG. 1 according to the same embodiment.

FIG. 3 is a flowchart illustrating the operation of the embodiment.

FIG. 4 is a flowchart showing in detail the process of step S6 of FIG. 3 according to the same embodiment.

FIG. 5 is a flowchart showing in detail the process of step S8 of FIG. 3 according to the same embodiment.

FIG. 6 is a diagram showing a state in which, after the database X and the database Y are synchronized, changes are made to both databases in the same embodiment.

FIG. 7 is a diagram showing a state where the database X and the database Y of FIG. 6 are synchronized in the same embodiment.

FIG. 8 is a diagram showing a state of a database after synchronization according to the embodiment.

FIG. 9 is a diagram showing a state where the same data A in both the database X and the database Y in the same embodiment are synchronized after the same details are modified but the details are the same.

FIG. 10 is a diagram showing a state in which, in the same embodiment, both the database X and the database Y are synchronized after the same data A has different expressions but the same contents are modified.

FIG. 11 is a diagram showing a state in which the same data A in both the database X and the database Y are synchronized after different contents are modified in the same embodiment.

[Explanation of symbols]

11 ... Microprocessor (CPU), 12 ... Storage device, 13 ... Synchronization program, 14 ... Database (database X), 15 ... Communication interface (communication-I
F), 16 ... Input interface (input IF), 17
... Input device, 18 ... Display control device (display CNT), 19
... Display device, 20 ... Display dot memory, 21 ... Printer interface (PRT-IF), 22 ... Printer (PRT), 23 ... Disk interface (FDD)
/ HDD-IF), 24 ... External storage device (FDD / HD
D), 25 ... Equipment having the same components as in FIG. 1, 26 ... Database (database Y).

Claims (5)

[Claims] 1. In a device having a database management function, when the same database existing on a plurality of devices is separately used by each device, the database can be different data, A synchronization unit that makes the data in the database the same, and a unit that has, as information, the change state of the data after the previous synchronization for each data in the database, synchronizes the databases on the plurality of devices. In case,
Based on the change state information by the means, only the data that has changed after the previous synchronization is targeted, and the data that has not changed is excluded from the synchronization target, so that the synchronization can be performed at high speed. Characteristic data management device. 2. When the data to be synchronized is corrected in each database, a judging means for judging the degree of correction of each data is provided, and each data has the same contents but different details. When the above is done, the data with more detailed contents is set as valid data, this valid data is added to another database, and the remaining undetailed data is deleted from the database. The data management apparatus according to claim 1, characterized in that 3. When the data to be synchronized is modified in each database, a judgment means for judging whether or not the contents of each data have different expressions but the contents are similarly modified. 2. When the respective data are judged to have been modified to have the same expression but different contents, the respective data are not synchronized and are left as they are in each database. Data management device. 4. When data to be synchronized is modified in each database, a judging means for judging whether each data is modified with different contents is provided, and each data is different contents. 2. The data according to claim 1, wherein when it is determined that the correction data has been corrected, one of the correction data is mutually added to the other database, and the original correction data is left without being deleted. Management device. 5. In a device that manages a database with an electronic organizer, a personal computer, etc., the same database existing on a plurality of devices is used separately for each device, so that the databases are different. When the data becomes data, the data in the database is made the same, and the data is controlled to have the change state of the data after the previous synchronization for each data in the database, and the databases on the plurality of devices are synchronized. In this case, based on the change state information, only the data that has changed after the previous synchronization is targeted, and the data that has not changed is excluded from the synchronization target, so that the synchronization is performed at high speed. Data management method.