JPH0293862A - Record retrieving mechanism in network type data base - Google Patents

Abstract

PURPOSE:To prevent idle reading and to improve access efficiency by preparing a record type referring file from a real data base, referring this file and reading the realizing value of a designated master record type. CONSTITUTION:A record type referring file preparing mechanism 2 once reads the real data base of a network type data base 1 and prepares a record type referring file 3. When the designating information of a retrieving subject record type and the request information of a master record position are received from a record taking-out mechanism 6, a master record position returning mechanism 4 successively reads the position of the real data base for the realizing value of the designated master record type from a head according to a request and returns the position to the master record taking-out mechanism 6. Thus, even when the real data base is accessed and a master record is successively taken out, idle reading is not generated to the real data base since the record realizing value to be next accessed is speedily known. Then, the access efficiency is improved.

Description

[Detailed Description of the Invention] [Object of the Invention] (Industrial Field of Application) The present invention relates to a record search mechanism in a network type database of a computer, and particularly to a record search mechanism in a network type database. This invention relates to a record search mechanism that improves access efficiency by eliminating idle reading of actual databases.

(Prior Art) Conventionally, in a network database, searching for records using all chains existing on the database requires a lot of time because a huge amount of data is handled.

A network type database basically has a parent record and a child record, and establishes a parent-child relationship between them using specific information called sesoto.

This set is internally realized by providing chain pointers between record realization values.

Furthermore, chain formation is complicated due to the following reasons, and as a result, a lot of time is required for searching.

1) A child record can become the parent record of another record.

2) One parent record can have multiple child records through multiple sets.

3) One child record can have multiple parent records using multiple sets.

4) A plurality of record realization values exist for each type of parent record and child record.

5) A plurality of child record realization values are chained to one parent record realization value.

(Problem to be solved by the invention) In the network type database as described above,
A record search that covers all chains in the database, by specific or all record types.
When the record realization value is retrieved sequentially from the real database and a chain search for child records is performed using it as a starting point, there is no chain to the next parent record, so the next parent record search is performed while sequentially accessing the real database. therefore requires a lot of processing time,
There was a problem with poor processing efficiency.

The present invention was made in view of the above circumstances, and in a network database, in a record search covering all chains, record realization values are sequentially extracted from the actual database for each specific parent record type, and this is used as a starting point. , when performing a chain search for child record realization values,
It is an object of the present invention to provide a record search mechanism in a network type database that can greatly improve access efficiency when sequentially retrieving parent records.

[Structure of the invention] (Means and effects for solving the problem) The present invention has the following features:
As shown in the figure, the network type database is equipped with a code type reference file creation mechanism 2, a record type reference file 3, a parent record position return mechanism 4, a record retrieval mechanism B, etc. 2 reads the real database of network database 1 once, and records type reference file 3.
Create. When the parent record position return mechanism 4 receives the designation information of the record type to be searched and the request information of the parent record position from the record retrieval mechanism G, the parent record position return mechanism 4 retrieves the actual database of the actual value of the specified parent record type from the record type reference file 3. The positions are read out in order from the beginning according to the above request and returned to the record retrieval mechanism.

The above record type reference file 3 reflects the physical arrangement of the record realization values in the real database as is by using only the record type (2 bytes) that each realization value has, and the real database can be accessed as in the past. If parent records are retrieved sequentially, many empty reads will occur, but by using the record type reference file 3 mentioned above, the record realization value to be accessed next can be immediately known, so empty reads to the actual database will occur. access efficiency is improved.

(Example) An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing one embodiment of the present invention.

In FIG. 1, l is a network type database (DB) having various records to be searched. 2 reads the real database of the network type database l once under the control of the processing mechanism 5, extracts only the 2-byte record type added to each record realization value, and creates the record type reference file 3. This is a record type reference file creation mechanism. 3 is a record type reference file (P) created by the record type reference file creation mechanism 2. 4 receives the specification information (a) of the record type to be searched and the request information (b) of the parent record position from the record retrieval mechanism 8, and retrieves the specified parent record type (
This is a parent record position return mechanism that sequentially reads out c) from the beginning and returns the actual database position (d) of the actual value to the record retrieval mechanism B. 5 is a processing mechanism (
3w-A). 6 is specification information (a) that specifies the type of record to be searched for the parent record position return mechanism 4.
In addition to sending the request information requesting the parent record position (
b), and in accordance with the request, receives the actual database position (d) of the actual value of the parent record type returned from the parent record position return device 4R4, and accesses the network type database l. Sea B
).

Here, the operation of the embodiment shown in FIG. 1 will be explained.

The record type reference file creation mechanism 2, under the control of the processing mechanism 5, reads the real database of the network type database l once, and uses only the 2-byte record type added to each record realization value. , the physical arrangement of record realization values in the actual database is mapped onto the record type reference file 3.

After the record type reference file 3 is created by the record type reference file creation mechanism 2, the record retrieval mechanism 6 notifies the parent record position return mechanism 4 of the record type (a) to be processed, and further requests the parent record position ( Issue b).

After receiving the record type to be processed (a) from the record retrieval mechanism 6, the parent record position return mechanism 4 receives a request for the parent record position (b), and then retrieves the specified parent record from the record type reference file 3. Read the type (c) from the beginning and find the actual database position (d) of its realized value.
is returned to the record retrieval mechanism 6. In this way, when the parent record position return mechanism 4 receives the parent record position request (b) after receiving the parent processing target record type (a) from the record retrieval mechanism 6, the parent record position return mechanism 4 Reads the specified parent record type (c) from the type reference file 3 in order from the beginning (that is, the record type next to the record type returned immediately before), and creates an actual database of actual values of each record type (C). The position (d) of the above request (b) is returned to the record retrieval mechanism 6.

The record retrieval mechanism 6 receives the actual database position (d) of the actual value of the specified record type (°C) from the parent record position return mechanism 4, and according to the information (physical position on the network type database 1) Access database l.

Such search processing prevents idle reading of the real database and improves access efficiency. That is, in the past, when accessing a real database and sequentially retrieving parent records, many empty reads occurred and the search efficiency was poor, but according to the above embodiment, the record type reference file 3
By using , the record realization value to be accessed next can be immediately known, so idle reads to the real database do not occur, and access efficiency is improved.

Note that the above-described search mechanism can be applied to troubleshooting and reorganization of network databases.

[Effects of the Invention] As detailed above, the record search mechanism in the network database of the present invention includes a file creation mechanism that reads the actual database and creates a record type reference file, and a file creation mechanism that specifies the record type to be searched. , a record retrieval mechanism that issues a request for the parent record position, and upon receiving the specification and request from the same mechanism, refers to the record type reference file and requests the position of the actual database of the realization value of the specified parent record type. By adopting a configuration including a parent record position return mechanism that sequentially returns the record position to the record retrieval mechanism according to the above, idle reads to the real database do not occur, and access efficiency can be improved.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing one embodiment of the present invention. ■...Network database (D13) 2...
- Record type reference file creation mechanism, 3... Record type reference file (P), 4... Parent record position return mechanism, 5... Processing mechanism (SW-A), [i.
...Record ejection mechanism (5W-8). Applicant's agent Patent attorney/certified attorney Takehiko Suzue

Claims (1)

[Claims] In a network type database, there is a file creation mechanism that reads the actual database and creates a record type reference file, a record retrieval mechanism that specifies the record type to be searched and requests the parent record position, and specifications and requests from the same mechanism. and a parent record position return mechanism that refers to the record type reference file and sequentially returns the actual database position of the actual value of the specified parent record type to the record retrieval mechanism in accordance with the above request. A record search mechanism in a network type database characterized by the following.