JPH10207753A - Automatic data transfer control device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent the mixing of data not satisfying a restriction condition by judging whether updated data satisfies the restriction condition of another data base to which the data are to be transferred, and when the restriction condition is satisfied, transferring the updating data to the other data base. SOLUTION: A restriction condition storing part 3 stores the restriction conditions of respective data bases in each data base. When the data of each data base 1 are updated by application 11, a restriction condition judging part 5 is informed of the updated information. The judging part 5 checks whether a restriction condition corresponding to the updated data has been registered in the restriction condition storing part 3 correspondingly to a data base 2 to which the updated data are to be transferred or not by retrieving the storing part 3. When the restriction condition has been registered, whether the updated data satisfies the restriction condition or not is checked. When the restriction condition is satisfied, the transfer of the updated data is determined and the updated data are transferred to the data base 2 through a data transfer control part 7.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an automatic data transfer control device for transferring data between a plurality of databases, for example, an automatic data transfer control device for transferring data between a common database and a personal database in a long-term transaction. .

[0002]

2. Description of the Related Art Data transfer between a plurality of databases is performed periodically, for example, once a day, or manually, such as when an operator executes an ftp command from a command line, or transmitted. Conventionally, such data transfer is merely transfer, which is performed when the original data is updated.

[0003]

In a database, there is a demand that data to be stored must satisfy predetermined constraints, but in the above-mentioned conventional data transfer, the data is transferred to the database and stored. The problem is that data that does not satisfy the constraints is also stored because it does not check whether or not the data satisfies such constraints, but simply accepts and stores all data that is transferred. is there.

[0004] The present invention has been made in view of the above,
An object of the present invention is to provide an automatic data transfer control device capable of transferring only data satisfying a constraint condition to each transfer destination database.

[0005]

To achieve the above object, according to the present invention, there is provided a constraint condition storage unit for storing, for each database, a constraint condition imposed on data stored in each database; When data stored in a certain database is updated and the updated data needs to be transferred to another database, the updated data satisfies the constraint conditions of the other database stored in the constraint condition storage unit. The gist of the present invention is to have a constraint condition judging unit for judging whether or not the update data is transferred, and a transfer unit for transferring the update data to another database satisfying the constraint condition when the constraint condition is satisfied as a result of the judgment.

According to the present invention, when data stored in a certain database is updated,
It is determined whether or not the update data satisfies the constraint conditions of another database at the transfer destination. If the update data satisfies the constraint conditions, the update data is transferred to another database.

[0007]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of an automatic data transfer control device according to one embodiment of the present invention. The automatic data transfer control device shown in FIG.
1, the data of the database 1 is updated, and the updated data is to be transferred to another database 2. The constraint storage unit 3 stores the constraints imposed on the data on each database. A constraint condition judging unit 5 for judging whether the update data satisfies the constraint condition stored in the constraint condition storage unit 3, and as a result of the judgment by the constraint condition judging unit 5, the update data satisfies the constraint condition. If it is, the data transfer control unit 7 executes the transfer of the update data. Although the constraint condition storage unit 3 stores the constraint condition of each database for each database, the constraint condition storage unit 3 may be provided for each database, or may be provided in common for each database, and each It may be set corresponding to the database.

Next, the operation of the automatic data transfer control device shown in FIG. 1 will be described with reference to the flowchart shown in FIG.

When the data in the database 1 is updated by the application 11, this update information is notified to the constraint condition judging unit 5, and the constraint condition judging unit 5 sends the constraint condition for the updated data to the database 2 to which the update data is transferred. Is checked by searching the constraint storage unit 3 to determine whether or not it is registered in the constraint storage unit 3 (step S10). If registered, it is checked whether or not the update data satisfies the constraint (step S20). If the constraint conditions are satisfied, the transfer of the update data is determined, and the update data is transferred to the database 2 via the data transfer control unit 7 (step S3).
0). Note that, when the constraint condition is not registered (step S10) or when the update data does not satisfy the constraint condition (step S20), the transfer of the update data is not executed.

Next, an example of the operation will be described with reference to FIG.

In FIG. 3, a database for storing design conditions is assumed, and the design information includes a design and a program. Also, A, B, and C exist in both the design and the program. The result of implementing the design A is a program A, the result of implementing the design B is a program B, and the result of implementing the design C is a program C. And

In the database 1, as a constraint condition, the design update date is later than the program update date (design update date ≦ program update date), and the program is not compiled normally. The database 2 defines that the design update date is earlier than the program update date (design update date> program update date) as a constraint, and that the program is compiled normally. It is assumed that

In an initial state, as shown in FIG. 3, designs A, B, C and programs A, B,
C is stored, and all of these designs and programs have the design update date ≦ the program update date, the program has not been compiled normally, and nothing is stored in the database 2.

In the initial state thus set,
When the programs B and C in the database 1 are changed and then compiled normally, the compiled programs B and C are transferred from the database 1 to the database 2 when the compilation is normally completed, and Is stored as shown in FIG.

Next, when the design B is changed in the state 1, the design B is not transferred to the database 2 but remains stored in the database 1 because the design update date ≦ the program update date. .

[0017]

As described above, according to the present invention,
When data stored in one database is updated, it is determined whether this updated data satisfies the constraints of the other destination database, and if so, the updated data is transferred to another database Therefore, only data that satisfies predetermined constraints defined for each database is stored in each database, and data that does not satisfy the constraints is not mixed.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an automatic data transfer control device according to an embodiment of the present invention.

FIG. 2 is a flowchart showing the operation of the automatic data transfer control device shown in FIG.

FIG. 3 is an explanatory diagram illustrating an operation example of the automatic data transfer control device illustrated in FIG. 1;

[Explanation of symbols]

 1, 2 database 3 constraint condition storage unit 5 constraint condition judgment unit 7 data transfer control unit

Claims (1)

[Claims] A constraint storage unit for storing, for each database, a constraint condition imposed on data stored in each database; a data stored in a database is updated;
When it is necessary to transfer the update data to another database, a constraint condition determination unit that determines whether the update data satisfies the constraint condition of the other database stored in the constraint condition storage unit, A transfer unit that transfers the update data to another database that satisfies the constraint condition when the result of the determination satisfies the constraint condition.