JP2001014192A - Device for managing database - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a database managing device by which re-execution (undo) in a case except an operational level is easily executed. SOLUTION: The device is constituted in such a way that the contents of a master database MDB are not actually updated and information corresponding to the history of updating based on an updating request is stored in a local database LDB in place of it when the request for updating records stored in the master database MDB to be updated is inputted from an input part 11 by key and, then, the contents corresponding to those after updating, which are stored in MDB, are displayed in a display part 12, based on the information when the contents of the master database MDB are displayed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database management apparatus having a function of undoing an update process for a database.

[0002]

2. Description of the Related Art In a database, a record A
Is updated, and then record B and record C are sequentially updated. If the user notices a mistake in updating record A after updating record C, the user manually operates only record A. If you want to make corrections and return to the state before the update, but the data to be updated is relatively large,
Alternatively, when the number of records to be updated is large, the records can be quickly returned to the state before the update by using an undo function generally provided in the computer program for database management. .
The contents of the update include new creation, change, and deletion of a record.

In the undo function, when record A is returned to the state before update when record C is updated,
The update operation is performed in order to return to the state before the update, that is, in the order of the record C, the record B, and the record A, all the update operations performed after the update of the record A are undone. It is a redo function at the operational level.

[0004]

However, in the above-mentioned conventional undo function, even when it is desired to return only the record A to the state before the update, the records B and C are also returned to the state before the update. Imposes on the user the re-updating of records B and C, which is inconvenient.

The present invention has been made in view of such circumstances, and when a database to be updated is requested to update data stored therein, the database is actually updated. Instead, storing information corresponding to the update history that can be performed based on the update request instead, for example, when displaying the contents of the database,
By displaying the content corresponding to the updated content stored in the database based on the information, it is possible to provide the same interface as the conventional display content, and to actually update the content of the database. An object of the present invention is to provide a database management apparatus that can easily be redone (undo) at a level other than the operational level.

[0006]

According to a first aspect of the present invention, there is provided a database management apparatus which, when a request for updating data stored in a target database is made, updates the database based on the update request. Storage means for storing information corresponding to the history of, and output means for outputting, based on the information stored in the storage means, contents corresponding to the updated information stored in the database. I do.

[0007] A database management device according to a second aspect of the present invention comprises:
The database management device according to the first aspect of the present invention is characterized in that the database management device further comprises a deletion unit that deletes the corresponding information stored in the storage unit when there is a request to cancel the data update request.

[0008] A database management device according to a third aspect of the present invention comprises:
The database management device according to the first or second aspect of the present invention is characterized in that the database management device further includes an updating unit that updates the data stored in the database based on the information stored in the storage unit.

In the present invention, when an update request for data stored in a target database is made, the data stored in the database is not actually updated, but the update request is not issued. The information corresponding to the update history that can be performed based on the stored information is stored, and based on the stored information, the content corresponding to the updated content stored in the database is output. By displaying, it is possible to display substantially the same update content as when updating is performed in the conventional database. On the other hand, since the content of the database is not actually rewritten, it is necessary to redo the operation at a level other than the operational level ( Undo) and other functions can be easily performed.

Further, according to the present invention, when there is a request for canceling a data update request to the database (for example, a request for undo), the information corresponding to the update history is deleted. Only the information corresponding to the corresponding request can be deleted, whereby the undo of the data update can be freely performed without depending on the operation procedure.

Further, according to the present invention, the data stored in the database is updated based on the information. Therefore, for example, when a user completes a certain amount of update work (the above two inventions). Does not actually rewrite the database), but the database can be updated to the latest contents including operations such as undo.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below in detail with reference to the drawings showing the embodiments. FIG. 1 is a block diagram showing a configuration of a database management device 1 according to the present invention. In FIG. 1, reference numeral 1 denotes a database management device according to the present invention configured as a user terminal computer. The database management device 1 includes a CPU 10, an input unit 11, a display unit 12, a ROM 13, a RAM 14, a local database LDB, and A communication interface (I / F) 15 is provided.

The CPU 10 executes various processes necessary for the operation of the database management device 1 based on a computer program stored in the ROM 13.

The input unit 11 is an input device including a keyboard, a mouse, and the like, and inputs update (new, changed, or deleted) information or instructions to the database.

The display unit 12 includes a display device such as a liquid crystal display (LCD) or a CRT display.
The various setting conditions input from the CPU 10 and the operation state of the CPU 10 are displayed. Note that by providing a configuration including a touch panel type display device instead of this, it is possible to omit part or all of the input unit 11 described above.

The ROM 13 is a rewritable ROM such as an EPROM, and stores various computer programs necessary for the operation of the CPU 10.

The RAM 14 includes an SRAM or the like, and stores temporary data generated when a computer program is executed.

The communication I / F 15 is an interface for connecting to a network such as a LAN, the Internet, an intranet, and a public telephone line network. Here, a master database MDB connected to the network is connected via the communication I / F 15. Connected. Note that the communication I / F 15 may be configured as SCSI, and the master database MDB may be connected without passing through a network.

FIG. 2 is a diagram showing a configuration example of the master database MDB. The master database MDB is a database managed by a general-purpose database management program, and is configured here as an employee information database. As shown in FIG. 2, the information (attributes) stored in the master database MDB is an employee number, a name, an address, a postal code, a telephone number, a department, a date of birth, and the like. Is set here so that the contents cannot be duplicated in a plurality of records.

The database management device 1 has a local database LDB. FIG. 3 is a diagram illustrating a configuration example of the local database LDB. The local database LDB basically has the same data structure as the master database MDB, that is, has the same attributes,
Here, two local exclusive attributes are added. The local-only attribute is management information when recording an update history in the master database MDB, and includes SEQ (sequence) and revocation C (revision code).

The SEQ is a serial number that is automatically assigned when a new record is registered in the local database LDB by the CPU 10.
A four-digit number such as 1 "," 0002 ", etc. The revision C is a type of update of a record newly registered in the local database LDB with respect to the master database MDB, that is, new (A), change (C), Or, it is a code indicating D (deletion).

The contents of the employee number in the local database LDB may be duplicated as described in detail later, so that the contents are set to be duplicated in a plurality of records. Further, as the local-only attribute, information such as a flag can be used instead of the above. Further, the content stored in the local database LDB is the master database MDB.
It is not necessary to provide the same data configuration as that described above. For example, the configuration may be such that only the attribute information in the record is retained, and the database may not be a database if the change history remains.

Next, how the contents of the local database LDB are registered will be described with reference to FIGS.

For example, first, the master database MDB
In the record of the employee number "1909", if the user moves due to transfer or the like, the contents of the "address", "postal code", and "telephone number" of the master database MDB are changed in connection with this. Shall be. However,
At this stage, the database management device 1 according to the present invention does not substantially update the master database MDB, but instead registers the updated contents in the local database LDB. That is, the content including the changed information is registered in the local database LDB in a record unit, and here, the first number “0001” as “SEQ” and the content of the update in “retrofit C” are stored. “C” indicating “change” is registered respectively.

For example, when the record of the employee with the employee number "1909" is subsequently deleted due to retirement, the local database LDB is similarly stored in the local database LDB without changing the contents of the master database MDB. Register history. In other words, the content of each attribute remains the same as the content at the time of the change described above, and “SEQ” is the next serial number. ”
0002 ", and" D "indicating" removal "is registered in" revision C ".

Further, for example, a new employee number "191"
In the case where an employee who becomes "1" enters the company, the employee number "191" is similarly stored in the local database LDB.
A new record of “1” is created, the contents of each attribute are registered, and the next sequential number “000” is set as “SEQ”.
3 ”and“ A ”indicating“ new registration ”are registered as“ revision and abolition C ”, respectively.

The database management apparatus 1 according to the present invention is configured as described above. Basically, during the update operation in the database management apparatus 1, the actual update processing to the master database MDB is not performed. . Instead, the update history is registered in the local database LDB configured as a storage means in the present invention, and the local database LD is stored in a time zone such as at night when a communication load is not applied to the network.
B stores the update history registered in master database MD
B to the master database M based on the update history.
It is configured to rewrite the contents of the DB to the latest information.

In the present embodiment, the information stored in the local database LDB is referred to as "update history" here. However, the master database MDB is actually stored before the transfer processing is performed as described above. Has not been updated and is only displayed on the display unit 12 as if it had been updated. The “update history” does not directly indicate the so-called update history of the master database MDB.

However, during the updating operation of the database management apparatus 1, it is necessary to always display the latest information on the display unit 12. Next, this function will be described.

FIGS. 4 to 7 are flow charts showing the processing contents of the CPU 10 of the database management apparatus 1 according to the present invention.
FIG. 5 shows a process for updating (new, changed, or deleted) data, FIG. 6 shows a process for undoing, and FIG. 7 shows a latest record search subroutine.

First, the processing at the time of inquiry (display) shown in FIG. 4 will be described. For example, in response to the user keying in a specific employee number (or a range designation for designating a plurality of employee numbers) from the input unit 11, this is accepted (step 1-1), and the latest A record search subroutine is executed (step 1-2), and the latest version of the record corresponding to each received employee number is read from the local database LDB or the master database MDB. Then, the read record of the latest version is displayed on the display unit 12 in a form (or table) designated in advance (step 1-3), and the process is terminated.

Next, the processing at the time of updating shown in FIG. 5 will be described. For example, in response to the user keying in an employee number to be updated (or a range designation for designating a plurality of employee numbers) from the input unit 11, this is accepted (step 2-1), and the latest record described later is input. A search subroutine is executed (step 2-2), and the target record is displayed on the display unit 12 as in step 1-3 in FIG.
Subsequently, in response to the user's key input of the update content from the input unit 11, the update content is accepted (step 2-3), and the update content is added (registered) to the local database LDB as described above (step 2-4). ), End this processing.

Next, the processing at the time of the undo shown in FIG. 6 will be described. For example, in response to the user's key input of an employee number to be updated (or a range designation for designating a plurality of employee numbers) from the input unit 11, this is accepted (step 3-1), and the target employee number is entered. It is confirmed whether or not a record corresponding to the above exists in the local database LDB (step 3-2). If the corresponding record does not exist in the local database LDB, the present process is terminated.
On the other hand, if the corresponding record exists in the local database LDB, the fact that the undo is possible is displayed on the display unit 12, and based on the number of “SEQ” specified in the same manner in step 3-1. Only the specified record from the applicable records is stored in the local database LDB
(Step 3-3), and the process ends.

Finally, the latest record search subroutine shown in FIG. 7 will be described. First, based on the "employee number" specified by key input or the like, a record of the corresponding "employee number" is searched from the local database LDB (step 4-1). Then, it is checked whether or not the record is in the local database LDB (step 4-2). If the record is not in the local database LDB, the record is stored in the master database MDB (it always exists here). Is read as the latest record via the communication I / F 15 (step 4-
3), end this processing. On the other hand, if it is in the local database LDB, the latest record is searched from the corresponding record, and this processing ends. In the search for the latest record in the local database LDB, first, among the corresponding records in the local database LDB, the record with the largest number of “SEQ” is read as the latest record. At this time, "SE
"Revision C" corresponding to the record with the largest number "Q"
Is "D", this record has been deleted and is not displayed.

FIG. 8 is a diagram showing the contents when the latest record is displayed based on the local database LDB shown in FIG. 2 and the master database MDB shown in FIG. For the record of employee number "1909",
“00” having the largest “SEQ” number in this record
02 ”, so it is not displayed.
The record of the employee number “1911” is simply added. The records of the remaining employee numbers have not been updated and are displayed as they are.

[0036]

As described above in detail, in the database management apparatus according to the present invention, when a request for updating the data stored in the target database is made, the data is actually stored in the database. Without updating the stored data, storing information corresponding to an update history that can be performed based on the update request, and outputting the corresponding content after the update stored in the database based on the stored information. Because, for example, by displaying the obtained contents, it is possible to display substantially the same updated contents as when updating is performed in the conventional database, while actually, the contents of the database are displayed. Since it has not been rewritten, functions such as redo (undo) at other than the operational level can be easily performed.

Further, when there is a request for canceling a data update request to the database (for example, an undo request), the corresponding information is deleted from the information corresponding to the update history. Can be deleted, thereby undoing the data update freely without depending on the operation procedure.

Further, according to the present invention, since the data stored in the database is updated based on the information, for example, when a user completes a certain amount of update work (the above two inventions). Does not actually rewrite the database), the present invention has an excellent effect that the database can be updated as the latest contents including the operation such as undo.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a database management device according to the present invention.

FIG. 2 is a diagram illustrating a configuration example of a master database.

FIG. 3 is a diagram illustrating a configuration example of a local database.

FIG. 4 is a flowchart showing the contents of a data inquiry (display) process by the CPU of the database management device according to the present invention.

FIG. 5 is a flowchart showing the contents of a data update (new, change, delete) process by the CPU of the database management device according to the present invention.

FIG. 6 is a flowchart showing the contents of an undo process by the CPU of the database management device according to the present invention.

FIG. 7 is a flowchart showing the contents of a latest record search subroutine process by the CPU of the database management device according to the present invention.

8 is a diagram showing the contents when the latest record is displayed based on the local database shown in FIG. 2 and the master database shown in FIG.

[Explanation of symbols]

 1 database management device 10 CPU LDB local database MDB master database

Claims (3)

[Claims] A storage unit for storing information corresponding to an update history based on the update request when an update request for data stored in the database is issued to a target database; Output means for outputting, after the update, the contents stored in the database based on the information stored in the storage means. 2. The database management apparatus according to claim 1, further comprising a deletion unit that deletes corresponding information stored in the storage unit when a request to cancel the data update request is issued. 3. The database management device according to claim 1, further comprising an updating unit that updates the data stored in the database based on the information stored in the storage unit.