JPH034365A - Data base operation processing system - Google Patents

Abstract

PURPOSE:To accelerate a DB operation processing from a user program by issuing the execution request of a registered DB operation by setting the identification name of the registered DB operation as a parameter when it is executed. CONSTITUTION:A pre-processor part 35 issues a pre-compilation request to a data base managing system DBMS 40b, and reads a source text in a source program 21b to be pre-processed one by one. When the source text is not a DB operation text, the source text is written out as a program after change. When the source text is the DB operation text, the pre-compilation request is issued to the DBMS 40b. A correspondence table in a DB 50 is updated based on the above result, and the DB operation text is converted to the source text which issues the execution request of the registered DB operation, and writes it to a source program after change. After such processing is performed for all source texts, a pre-compilation completion request and a storage request to the DB 50 of the correspondence table are issued to the DBMS 40b, then, the processing is completed.

Description

Detailed Description of the Invention [Field of Industrial Application] The present invention relates to a database (hereinafter referred to as rDBJ) operation processing method in a system that accesses a database using a database management system that provides a precompile function. .

[Prior art] Recent database management systems (hereinafter referred to as rDBMSJ)
The mainstream of application program interfaces provided by companies such as ``Embedded'', in which DB operation statements are written directly in the program, has become mainstream. The purpose of the embedded type is to improve user-friendliness by writing the DB operation statements (commands) used in terminal operations in the program as they are (and converting them into programming language statements, i.e., preprocessing). By analyzing the DB operation statement during preprocessing and converting it into an easy-to-execute format (i.e., precompilation),
The purpose is to enable faster processing during program execution.

Specific examples of this include D , D , Chamb
The paper “5upport for Repetit” published in NCM Transactions on Database Systems, Volume 6, No. 1 by Erl In et al.
ive Transact.

1onsand Ad Hoe Queries in
System R″′ (D.

D. Chamberlin et all “5uppo
rt for RepetitiveTransac
tions and Ad Hoe Quer
ies in System R”, ACM
Transactions on Database
Systems, vol. 6. Nal, March +
981. pp, 7O-94).

The above-mentioned paper discusses a method for implementing the precompile function in a relational database management system. FIG. 4 shows an outline of the system of the above-mentioned known example. Here, the DBMS 40a includes a precompiler section 4I and a runtime system section 42a. The precompiler unit 41 preprocesses the source program 21a of the user program, and converts the program 2
The DB operation statements written in 1a are extracted, their analysis is performed, execution procedures are determined (so-called optimization), and executable code is generated. The executable code generated for each DB operation statement is called a section, and the entire section generated from one program is collectively called an access module. The precompiler IIfJ41 stores the management information of this access module and the access module in the DB50. Furthermore, a modified source program 22a is created in which the DB operation statements in the program 21a are replaced with call statements that use the corresponding access module name, section number (identifier), etc. as parameters.

After preprocessing the program, the user creates an executable program 20a by running it on a compiler of the language in which the program is written. Thereafter, by starting the executable program 20a, operation B is executed as necessary. When a program is executed, the runtime system section 42a of the DBMS 40a is called. Runtime system section 42
Based on the parameters passed when a is called,
Loads the corresponding access module into main memory and executes the specified section.

In the method described above (precompile function), the analysis of DB operation statements written in the program is performed at the time of preprocessing, so the analysis of DB operation statements during program execution can be omitted, reducing processing time. can do.

On the other hand, in the case of a program (user-friendly interface It in FIG. 4) that accepts a user's request from the terminal IO and passes the request to the DBMS 40a,
The requested DB operation is determined at the time of program execution, not at the time of preprocessing. For such programs,
If you use an interface that specifies DB operation statements when executing a program,
Since the DB operation statement itself is passed between the receiver and the MS,
When executing a program, it is necessary to analyze the DB operation statement. In the example shown in FIG. 4, the runtime system unit 42a uses the DB
After parsing the operation statement and dynamically generating sections,
Run that section.

[Problem to be solved by the invention]

As mentioned above, programs that determine the DB operation required at the time of program execution are collectively referred to as a DB access system. Examples of this DB access system include a multimedia DBMS based on a relational DBMS, an interface program for terminal users of each DBMS, and a utility program for editing and outputting DB contents.

In the case of the above-mentioned DB access system, the DB operation to be executed is not determined until the program is executed, that is, until a request from the user is received. Therefore, it is necessary to use an interface that receives and passes DB operation statements during program execution. However, in reality, there are routine operations for terminal users or user programs that use the DB access system. However, in the above-mentioned conventional technology, the DB access system must receive and pass the DB operation statement each time even if it is a routine operation. In other words, there is a problem in that it is not possible to benefit from faster processing due to precompilation.

In addition, in the case of a user program that uses a DB access system to perform DB operations, even if the DB operation is decided, there is no interface to request precompilation from the DB access system to the DBMS side, so precompilation also speeds up processing. cannot benefit from the change.

Furthermore, the DB access system, like the above-mentioned conventional technology, is a multimedia DB using relational DBMS.
In the case of a BMS, it is necessary to convert the DB operation function provided by this DB access system to the DB operation provided by the DBMS, and performing this conversion operation every time a request is made will lead to a decrease in processing efficiency. There are also problems.

The present invention has been made in view of the above circumstances, and its purpose is to solve the above-mentioned problems in the conventional technology, and to enable DB operations to be determined at the time of program execution.
An object of the present invention is to provide a DB operation processing method that makes it possible to use the precompile function of a DBMS even from an access system.

In other words, the purpose of the present invention is to extract the DB operation statements written in the program at the time of preprocessing, perform so-called optimization, and generate executable code for the above-mentioned routine operations. In this way, it is an object of the present invention to provide a DB operation processing method that makes it possible to benefit from faster processing due to precompilation.

[Means to solve the problem]

The above-mentioned object of the present invention is to
A DB access system that accepts a DB operation request from a terminal user or user program for an MS, delivers the DB operation request to the DBMS and requests its execution, and executes a DB operation corresponding to the DB operation execution request. In the system consisting of the DBMS, the DB access system receives DB operations from a terminal user or a user program! ! When receiving a recording request,
transmitting a precompilation request for the DB operation to the DBMS; and upon receiving a request to execute the registered DB operation from a terminal user or user program;
Precompiled DB corresponding to the registered DB operation
A step of requesting the DBMS to execute the operation is provided, and a step of precompiling the DB operation when the DBMS receives a request to compile the DB operation from the DB access system. In the characterized DB operation processing method or the system, the DB access system preprocesses a program that uses the DB access system, extracts a DB operation request from the program, and preprocesses it to the DBMS. A preprocessor unit is provided that makes a compile request and changes a DB operation request in the program into a registered DB operation execution request for the DB access system based on the result, and the DB access system When receiving a registered DB operation execution request issued when executing the user program preprocessed by
This is achieved by a DB operation processing method characterized by comprising the step of requesting the MS to execute a precompiled DB operation corresponding to the DB operation requested to be executed.

[Operation J] In the DB operation processing method according to the present invention, when a terminal user or user program using a DB access system has a fixed DB operation request that is used repeatedly, the DB operation is registered. request. When making a DB operation registration request, the request is made by specifying the details of the DB operation to be registered and its identification name. If a registered DB operation is to be executed, a request to execute the registered DB operation is issued using the identification name as a parameter.

An example of the request is shown in FIG. Here, the employee file (E
We have registered a DB operation request CI that searches for the name (NAME) of employees belonging to the department (DEPT) with the specified department name ($DEPT) from MPLOYEE, and then searches for the number of employees (COUNTD). 80), it is assumed that the terminal user registers routine operations. The registered DB operation execution request is issued, for example, as shown in FIG. 81.

When a DB operation registration request is received, the DB access system issues a preprocessing request to the DBMS using the corresponding DB operation statement and its identification name as parameters. DBMS
converts the DB operation statement requested for precompilation into an executable format, stores it in the DB, and then returns to the DB access system.

In the example shown in FIG. 3, two DB operations, such as 82, are registered. When a request to execute a registered DB operation is received, the DB access system requests the DBMS to execute a section corresponding to the DB operation with the specified registered name.

Furthermore, when a user creates a program that uses the DB access system, a request to the DB access system is directly written in the program. The user submits this program to the preprocessor of the DB access system and changes requests to the DB access system into statements in the language in which the program is written. The program is then run through a compiler for the language in which it was written to create an executable program.

The preprocessor section of the DB access system analyzes the program and extracts requests to the DB access system. For each request, the request is converted into a request to the DBMS, and a precompile request is issued to the precompiler section of the DBMS. Based on the precompilation result, a modified source program is generated in which the operation request is converted into a registered DB operation execution request for the DB access system.

The preprocessor section issues a registration request as an access module after precompilation of all requests is completed.

When the user program is executed, a registered DB operation execution request is received from the user program, and the same processing as in the case of registration from the user program described above is performed.

Through the above-described processing, the DB access system
The precompile function of MS can now be used, making it possible to speed up processing.

〔Example〕

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

FIG. 1 is a diagram illustrating the overall configuration of an embodiment of the present invention. The user uses a terminal 10 and a terminal interface 15,
Alternatively, a process is requested to the DB access system 30 via the user program 20b.

The DB access system 30 analyzes the request from the user and requests the 08MS 40b to perform the corresponding DB operation. 0
The 8MS 40b performs DB operations within the DB 50 according to the request.

Moreover, FIG. 2 is a diagram showing the minimum equipment configuration for implementing the present invention. 08MS, which is a component of the present invention, is described in 1.
40b, DB access system 30. The user program 20b and the terminal interface 15 run on the computer 60. The secondary storage device 70 stores the DB 50 and data files used by each program. The terminal 10 is used by a terminal user to utilize the DB access system 30 or to start the user program 20b via the terminal interface 15. In FIG. 2, only one computer is shown, but the above-mentioned components may be arranged on a plurality of computers connected by a network.

A processing method regarding registration and execution of routine B operations will be described below. It is assumed that the 08MS 40b provides a precompile function as shown in the prior art described above.

” The series of DB access systems 30 includes a request control unit 31 . A DB operation analysis execution unit 32 that analyzes a DB operation request and requests the MS 40b to execute it. It consists of a DB operation registration unit 33 that requests the 08MS 40b to generate and register an access module in response to a DB operation registration request, and a registered DB operation execution unit 34 that requests execution of the registered DB operation.

When a terminal user or user program 20b using the DB access system 30 makes a DB operation registration request, the request is made by specifying the contents of the DB operation to be registered and its identification name. When a registered DB operation is desired to be executed, a registered DB operation execution request is issued using the identification name as a parameter.

The details of each process of the DB access system will be described below.

(1) Request control processing The flow of processing by the request control unit 31 is shown in FIG.

The request control unit 31 first checks the request content (step 3+1). In the case of a DB operation analysis execution request,
Control is passed along with the specified DB operation request to the DB operation analysis execution unit 32 (step 312). In the case of a DB operation registration request, the specified DB operation request and its registered name are passed to the D and B operation registration section 33 (step 313).

Further, in the case of a request to execute a registered DB operation, the specified registered name is passed to the registered DB operation execution unit 34 (step 315). When each process is completed, the results are returned to the caller (step 314).

(2) DB operation analysis execution process The process flow of the DB operation analysis execution unit 32 is shown in FIG. The DB operation analysis execution unit 32 analyzes the content of the DB operation request (step 321) and generates a corresponding DB operation statement (step 322). After generation, the 08MS 40b is requested to analyze and execute (step 323).

Thereafter, the results are returned to the requester (step 324).

(3) DB operation registration processing The flow of processing of the DB operation registration section 33 is shown in FIG. D
The B operation registration unit 33 analyzes the specified DB operation request content (step 331) and generates a corresponding DB operation statement (step 332). Note that there may be multiple DB operation statements. In either case, a section number is set for each DB operation statement and specified along with the DB operation request! l
A correspondence table 90 with record names is created (step 333).

The above-mentioned correspondence table 90, as shown in FIG.
B Represented by a structure area including an array that associates the section group corresponding to the operation statement. The creator 91 is the name 1r11 of the user who requested the DB operation registration, and the program name 92 is the name 1Iji of the user program 20b or terminal interface 15 that issued the registration request. Operation ID
93 is a registered name. The correspondence table 90 further includes section numbers 95 and parameters 9 for the number of DB operation statements (94).
It has information of 6th class. After creating the correspondence table 90, the name specified along with the DB operation request is set as the DB operation registration name.
08 A request to start precompilation is issued to the MS 40b (step 334). Subsequently, a precompilation request for each DB operation statement is issued to the DBMS 40b (step 335). In the precompile request, a DB operation statement and its identification name (operation ID) are passed as parameters. When precompilation of all DB operation statements is completed, a precompilation end request is issued (step 336). After that, the above correspondence table 9
0 is stored in the DB 50 (step 337).

(4) Registration DB operation execution process The flow of processing of the registration DB operation execution unit 34 is shown in FIG. The registered DB operation execution unit 34 executes the specified registered DB
Using the name of the operation request (operation ID), user name (creator), and request source program name 92 as keys, a correspondence table 90 between the section numbers of the DB operation statements precompiled by the above process is retrieved from the DB 50 (step 341). . Then, while looking at the correspondence table 90, execute each section
Requests are made to the BMS 40b (steps 342 to 345).
).

Note that the storage of the correspondence table 90 in the DB 50 and its search are naturally performed via the DBMS 40b.

There is also a method in which the correspondence table 90 is held in the main memory and the process of searching from the DB 50 is omitted. In this case, the process of storing the correspondence table 90 in the DB 50 at the time of DB operation registration is performed as described above, but the process of erasing it from the main memory is not performed. Furthermore, when starting the DB access system 30, it is necessary to take out all the correspondence tables 90 onto the main memory. In this case, in order to improve the space efficiency of the main memory, a buffer area for the correspondence table 90 is prepared, and LRU (Last Recent
yUsed) method may also be considered.

Finally, the flow of processing of the runtime system section 42a of the DBMS 40b is shown in FIG. On the DBMS40b side,
In addition to the conventional processing, the following processing (4) to (6) is performed.

First, the contents of the request are checked (step 401), and the request is as follows: (1) The platform for the program start request loads the access module of the program into the access module management area (step 402).

After loading, control is returned to the requester.

(2) In the case of a DB operation statement analysis execution request, the received D
Analyze the B operation statement (step 403) and create an executable section (step 404).

After setting the execution environment (step 405), the section is executed (step 406). After completion, the execution result is returned to the requester (step 407).

This request is a request corresponding to a dynamic DB operation execution request. When an executable section is created by analyzing it during preprocessing, a request to execute the next section comes.

(3) In the case of a section execution request, set the execution environment of the corresponding section in the access module (Step 405), and execute the section (Step 406).
. After completion, return the execution result to the requester (step 407)
.

When executing a section, especially in the case of a search, an operation request for passing the search results is required, but this is not related to this patent and will therefore be omitted here.

(4) In the case of a precompilation start request, the identification name of the program to be precompiled or the DB operation statement group is received, and the management information of the access module is generated (step 408).

(5) In the case of a precompilation request, the DB operation statement is analyzed (step 409), and the section of the analysis result is associated with the access module management information (step 410).
411).

(6) In the case of a precompilation end request, the access module management information and the access module body are stored in the DB 50 (step 412).

According to the above embodiment, the precompile function of the DBMS 40b can be used from a program, and the processing speed can be increased.

Next, a method for precompiling a routine operation request to the DB access system 30 written in a program that uses the DB access system 30 will be described. This is because the preprocessor section 35 described above
This is achieved by analyzing ``b'' and issuing a precompilation request to the DBMS 40b.

The processing procedure of the preprocessor section 35 will be explained below according to the flowchart of FIG. 11.

The preprocessor unit 35 first issues a precompilation request to the DBMS 40b (step 351). after that,
The source sentences in the source program 21b to be preprocessed are read one by one (step 352), and steps 325 to 358 are repeated until there are no more source sentences.

If the source statement is not a DB operation statement, write the source statement as is as a modified program (step 35).
5). If the source statement is a DB operation statement, a precompile request is issued to the DBMS 40b (step 356).

Based on the results, the correspondence table 90 is updated (step 357), the DB operation statement is converted into a source statement for requesting the execution of a registered DB operation, and the source statement is written to the changed source program (step 358).

Once one or more processes have been completed for all source statements,
A precompilation end request (step 359) and a request to store the correspondence table 90 in the DB (step 360) are issued to the DBMS 40b, and the process ends.

As described above, it is possible to use the precompile function of the DBMS even for routine B operations written in a user program that uses the DB access system 30, and it is possible to speed up the processing.

It should be noted that each of the above embodiments is shown as an example of the present invention, and the present invention should not be limited thereto.

〔Effect of the invention〕

As described above in detail, in the present invention, when a terminal user or a user program using a DB access system requests registration of a standard DB operation and wants to execute the registered DB operation, the identification name is sent as a parameter. By issuing a request to execute a registered DB operation using
The access system issues a DB operation statement preprocessing request to the DBMS corresponding to the DBllk work registration required/unregistered request. After executing the preprocess, the DBMS converts the DB operation statement into an executable format, stores it in the DB, and returns it to the DB access system. When a request to execute a registered DB operation comes, the DB access system sends the execution request for the DB operation section with the specified registered name to the DBMS.
from the DB access system to the DBMS by performing
The preprocessing function will be available to speed up processing.

That is, according to the present invention, since the DB operation is determined at the time of program execution, the precompile function can be used from the B access system, and the DB operation processing from the terminal user or user program using the DB access system can be performed at high speed. It is possible to aim for

[Brief explanation of drawings]

Fig. 1 is a diagram explaining the overall configuration of a DB system showing an embodiment of the present invention, Fig. 2 is a diagram showing the minimum equipment configuration for implementing the present invention, and Fig. 3 is a request for DB operation registration from a terminal. Figure 4 is a diagram showing the overall configuration of a known example DB system, and Figure 5 is a diagram showing an example of the configuration of a correspondence table that maintains the correspondence between the DB operation that requested registration and the request identification name of record 1. diagram showing,
6 to 1t are processing flowcharts showing the operation of each part of the embodiment. IO = terminal, 15: terminal interface, 20a, 20
b user program, 21a, 21b: source program, 30: DB access system, 31: request control section, 32: DB operation analysis execution section, 33: DB operation registration section, 34: registered DB operation execution, 35. preprocessor Parts, 40a, 40b: DBMS, old/precompiler part, 42a, 42b Runtime system part, 50: DB
, 60, computer, 70 secondary storage device. Figure 2 0 0 U ← Figure 7 Figure 8 Figure

Claims (1)

[Claims] 1. For a database management system having a precompile function, accepting a database operation request from a terminal user or a user program, and passing the database operation request to the database management system to request its execution. In a system comprising a database access system and the database management system that executes a database operation corresponding to the database operation execution request, when the database access system receives a database operation registration request from a terminal user or a user program, transmitting a precompile request for the database operation to the database management system, and upon receiving a request to execute the registered database operation from a terminal user or a user program, transmitting a precompiled database corresponding to the registered database operation; a step of requesting the database management system to execute the operation; and a step of pre-compiling the database operation when the database management system receives a request to compile the database operation from the database access system. A database operation processing method is provided. 2. A database access system that accepts a database operation request from a terminal user or a user program, and passes the database operation request to the database management system to request its execution, targeting a database management system having a precompile function; In a system comprising the database management system that executes a database operation corresponding to a database operation execution request, the database access system preprocesses a program that uses the database access system and extracts a database operation request from the program. a preprocessor unit that issues a precompilation request to the database management system, and changes a database operation request in the program into a registered database operation execution request to the database access system based on the result; When the access system receives a request to execute a registered database operation issued when executing the user program preprocessed through the preprocessor section, the access system executes the database operation requested to the database management system. A database operation processing method comprising the step of requesting execution of a corresponding precompiled database operation.