JPH03250229A - Commitment control system - Google Patents

Abstract

PURPOSE:To accelerate an update processing by executing commitment control for regulating the data processing unit of a data base when a value totalizing the number of updated records and the number of scrolled records reaches a prescribed reference value. CONSTITUTION:When the value totalizing the number of records to be scrolled by a data display mechanism 11 and the number of records updated by a data updating mechanism 18 reaches the prescribed reference value, a commit control mechanism 14 executes the commitment control for regulating a transaction and is equipped with first and second counters 15 and 16 and a commit execution part 17. The first counter 15 counts the number of records scrolled on a screen by interlocking with a data display part 13, and the second counter 16 counts the number of updated record by interlocking with a data input part 19. Thus, even when a relational data base is handled, the update processing is accelerated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Object of the Invention] (Industrial Application Field) The present invention relates to a commitment control method, and particularly to a commitment control method for a computer system that executes updating processing of database data on a screen in real time.

(Prior Art) Generally, in a computer system that updates data in a database in real time on a CRT screen, data corresponding to the roux code in the database is displayed on one screen. Therefore, the update process that can be executed by the operator while referring to the CRT screen is for one screen, that is, for each code.

In such a system, when the data update process for a code is completed, a commit is automatically executed, thereby defining the code as one transaction. In this way, in a system where a code is displayed on one screen, transactions are defined on a per-screen basis, so the record before the record currently displayed on the screen has already been determined as a transaction. For this reason, for example, if a failure occurs while performing a key operation to update a record displayed on the screen, the update can be performed using roll pack processing at the time of failure. The state is returned to the state before the process was executed, but since the record on the previous screen has already been confirmed as a transaction as described above, it is possible to restart the update process from the currently displayed record.

However, relational database (RDB)
When dealing with a tabular database such as , multiple records are displayed on one screen instead of roucodes, so even if you commit in roucode units, it is not defined as a transaction. , instead of data for one screen, it becomes data for one row in the displayed table. When executing a commit, input/output processing is involved to write updated data to a file, so
Once commit is executed, the start of update processing for the next record will be delayed by the time required for the input/output processing.

For this reason, in systems that handle relational databases, if commits for specifying transactions are executed in code units as in the past, input/output processing will be performed on the same screen many times, and the processing speed of update processing will be reduced. A problem arises in which the performance is reduced.

In addition to controlling commit execution for each code, there is also a method to control commit execution by manual operation, but if multiple records are displayed on one screen, the data content displayed on the screen is changed on a per-code basis by scrolling, so the division between screens is unclear. For this reason, controlling the commit execution by manual operations places a very heavy burden on the operator, and there is also a risk that data may be destroyed due to operational errors. Therefore, in a system that handles a relational database, it is difficult to control commit execution through manual operations.

(Problem to be solved by the invention) Conventionally, when dealing with relational databases, a commit is executed for each row of data in the displayed table, which slows down the processing speed of update processing. There were some drawbacks.

This invention has been made in view of these points, and provides a commitment control method that can automatically execute commit on a screen-by-screen basis even when dealing with relational databases, and can speed up update processing. aim at something.

Composition of the Invention CMeans for Solving Problem 1) The commitment control method according to the present invention includes a display means for displaying data for a plurality of records read from a database on a screen, and data contents displayed on the screen by the display means. a data updating means for updating record by record, a scrolling means for scrolling the data displayed on the screen on the display means record by record, the number of records updated by the data updating means and the records scrolled by the scrolling means; and a commitment control means for executing commitment control for defining a processing unit of data in the database when the total value with the number reaches a predetermined reference value.

(Operation) In this commitment control method, commitment control is executed when the total value of the number of scrolled records and the number of updated records reaches the standard value, so the standard value is displayed on one screen. By setting the number of records to about the number of records, commitment control can be automatically executed on a screen-by-screen basis without putting a burden on the operator.

Therefore, even when dealing with a relational database, it is possible to perform update processing at high speed.

(Example) Hereinafter, the present invention will be described in detail with reference to the drawings.

FIG. 1 shows a computer system for implementing a commitment control method according to an embodiment of the present invention. This computer system includes a data display mechanism 11, a commit control mechanism 14, a data update mechanism 18,
Relational Database Control System Department (RDBC)
3) 21, a relational database (RDB) file 22, a CRT display 23, and a keyboard (KB) 24.

The data display mechanism 11 is for displaying data retrieved from the relational database file 22 in a table format on the CRT display 23, and includes a data retrieval section 12 and a data display section 13.

The data retrieval unit 12 retrieves data for a plurality of records from the relational database file 22 in cooperation with the relational database control system unit 21 . The data display unit 13 displays data for a plurality of records extracted by the data extraction unit 12 on the CRT display 23.

The data display mechanism 11 also has a function for scrolling up and down the data displayed on the CRT display 23 record by record.
This scrolling operation is performed by the operator using the keyboard 24.
Controlled according to key operations.

The data update mechanism 18 is for updating the data displayed on the CRT display 23 for each record, and includes a data input section 19 and a data update section 20.

The data input section 19 includes a keyboard 24 for use by an operator.
Receives data entered by key operations. The data update section 20 cooperates with the relational database control system section 21 to update specific record contents within the data displayed on the CRT display 23 based on the input data received by the data input section 19.

The commit control mechanism 14 executes commitment control to define a transaction when the total value of the number of records scrolled by the data display mechanism 11 and the number of records updated by the data update mechanism 18 reaches a predetermined reference value. It is equipped with first and second counters 15 and 16, and a commit execution unit 17.

The first counter 15 works in conjunction with the data display section 13 to count the number of records scrolled on the screen. The second counter 16 has a data input section 19
By linking with , the number of updated records is counted. The commit execution unit 17 executes commitment control in collaboration with the relational database control system unit 21 when the total value counted by the first and second counters 15.16 reaches the above-mentioned reference value. In this case, the reference value is preferably set to a value approximately equal to the number of records for one screen displayed on the CRT display 23. In addition, if no data update processing is executed, there is no need to perform commitment control, so in reality, the condition for executing commitment control is that at least data updates for the number of codes have been executed. becomes.

Next, with reference to FIG. 2, the relationship between transactions defined by the commitment control of the commit control mechanism 14 and the screen display state of the CRT display 23 will be explained. Here, for the sake of simplicity, an example will be explained in which the data displayed on one screen corresponds to seven records.

In FIG. 2(A), no scrolling operation is performed and CR
A case is shown in which all seven records R1 to R7 displayed on the screen 30 of the T-display 23 have been updated. In this case, if the reference value is set to 7, a commit will be executed when record R7 is updated, and the updated 7 records from records R1 to R7 will be transferred to the relational database file 22.
, and these are defined as one transaction.

FIG. 2(B) shows that after scrolling in three directions from records R1 to R3, the CRT display 23
4 records out of 7 records of RIO from record R4 displayed on the screen 30 of
5, Re, and R8 are shown as being updated.

In this case, if the reference value is set to 7, record R
Commit is executed when 8 is updated, and record R
Of the 8 records 1 to R8, 5 records R4 to R8 that have been updated are defined as one transaction.

Next, the commitment control operation of this embodiment will be explained with reference to the flowcharts of FIGS. 3 and 4. The flowchart in FIG. 3 shows the operation using the first counter 15, and the flowchart in FIG. 4 shows the operation using the second counter 16.

First, data for one screen is displayed on the CRT display 23. When the screen is scrolled in this state, a count request is issued from the data display section 13 to the first counter 15, and the routine shown in the flowchart of FIG. 3 is thereby executed. . However, in this case, since the update process has not yet been executed for any record, the count value of the second counter (counter 2) 16 is "0". Therefore, the Ai condition of the step is not established, and the commit is not executed.

When data is input from the keyboard 24, the record being displayed is updated based on the input data. At this time, a count request is issued to the second counter (counter 2) IB, which causes the routine shown in the flowchart of FIG. 4 to be executed.

In this routine, first, the value of the second counter is incremented by +1 from rOJ to "1" (step B1). As a result, the condition of step AI in FIG. 3 is satisfied, and the total count value of the count value of the second counter (counter 2) 1B and the number of scroll lines counted by the first counter 5 is obtained ( Step A2)
.

After that, if the screen is scrolled, the total count value calculated in step A2 (the number of updates up to that point +
It is determined whether the number of scroll lines) is greater than or equal to a reference value (step A3). If it is equal to or greater than the reference value, a commit is executed (step A4), and then the values of the first and second counters 15.16 (counter 1, counter 2) become "0".
” (step A5).

Furthermore, each time the update process is executed, the value of the second counter 16 is updated by +1 in step B1 of the routine in FIG. 4, and then the total count value (the number of updates so far + the number of scroll lines) is It is determined in step B2 whether or not the value is greater than or equal to the value. If the total count value is greater than or equal to the reference value, commit is executed (step B3), and then the first and second counters 15, 1B (counter 1, counter 2)
The value of is initialized to "0" (step B4).

In this way, in this embodiment, even if scrolling is never executed, a commit is executed when the number of updates reaches the reference value, but if no updates are executed even once, the database In order to speed up the update process, commit is not executed even if the number of scroll rows reaches the threshold value.

As described above, in this embodiment, commitment control is executed when the total value of the number of scrolled records and the number of updated records reaches the number of records displayed on one screen, which burdens the operator. Commitment control can be automatically executed on a screen-by-screen basis without requiring additional time. In addition, if no update has been executed even once, even if the number of scroll lines reaches the standard value, commit will not be executed.
The occurrence of wasteful I10 processing can be prevented, and the update processing speed can be further increased.

[Effects of the Invention] As described above, according to the present invention, even when dealing with a relational database, commit can be automatically executed in units of one screen, and update processing can be speeded up.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing a system configuration for realizing a commitment control method according to an embodiment of the present invention, and FIG. 2 shows the data display state and fumit of the display provided in the system shown in FIG. FIGS. 3 and 4, which show the relationship between control and control, are flowcharts explaining the operation of the system shown in FIG. 1, respectively. DESCRIPTION OF SYMBOLS 11... Data display wA, 14... Comint control mechanism, 18... Data update mechanism, 21... Relational database control system section, 22... Relational database file, 23... CRT display, 24 ···keyboard.

Claims (1)

[Claims] a display means for displaying data for a plurality of records read from a database on a screen; a data update means for updating the data content displayed on the screen by the display means for each record; and a data update means for updating the data content displayed on the screen by the display means A scrolling means scrolls record by record, and when the total value of the number of records updated by the data updating means and the number of records scrolled by the scrolling means reaches a predetermined reference value, the data of the database is updated. A commitment control method comprising: commitment control means for executing commitment control for defining processing units.