JPH11306071A - Hierarchy data management system and hierarchy data management program storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a hierarchy data management system and a hierarchy data management program storage medium in which maintenance of a data base is easier and an access speed is fast. SOLUTION: This device separately constructs two data bases that consist of a calling side data base 100 which is composed of a set of records where plural data with an ID101 attached for identifying each other are stored and a hierarchy data base 200 which consists of a set of records those which are records corresponding to the record on the calling side data base 100 with an ID 201 corresponding to the ID 101 imparted to each record of the calling side data base 100 imparted and are stored in hierarchy data which stipulate a hierarchy relation between the records of the calling side data base 100.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a hierarchical data management system having a database for managing hierarchical data and a storage medium for a hierarchical data management program.

[0002]

2. Description of the Related Art Hitherto, an RDB (relational database) has been widely used for managing hierarchical data such as a parts development diagram in a manufacturing industry and a personnel organization chart in a general company. For example, in an exploded view of an aircraft, a table describing data of main parts such as an engine, a wing, a tail, and a fuselage is created, and further, a table describing data of child parts constituting each part for each of these main parts. And then create a table that describes the data of the grandchild parts that make up each child part for these child parts. A database is built.

[0003]

However, when there are many types of parts and the level of the parts list is deep as in the case of a recent aircraft, the database having the above-described structure has a problem in searching for a part of a lower level. Requires a large number of tables to be accessed, which requires a long data processing.

In the case of a parts list, every time a design is changed,
In the case of a personnel organization chart, it is necessary to maintain the entire database every time a personnel change or organizational revision occurs, and therefore, there is a problem that complicated management must be performed. The present invention has been made in view of the above circumstances, and has as its object to provide a hierarchical data management system and a hierarchical data management program storage medium in which database maintenance is easy and access speed is high.

[0005]

According to a first hierarchical data management system of the present invention for achieving the above object, in a hierarchical data management system including a database for managing hierarchical data, a hierarchical data management system is provided. A caller database consisting of a set of records each storing one or more data, each of which has an ID assigned thereto, and each I corresponding to each ID assigned to each record of the caller database.
Two databases, each of which is a record corresponding to a record of the calling database and denoted by D, which is a set of records storing hierarchical data defining a hierarchical relationship between the records of the calling database, are provided. It is characterized by being configured separately.

The second object of the present invention to achieve the above object is as follows.
The hierarchical data management system includes a caller database comprising a set of records each storing one or more data, each of which is provided with an ID for identifying each other, and is attached to each record of the caller database. A hierarchical database consisting of a set of records, each of which corresponds to a record of the calling database and has hierarchical data defining a hierarchical relationship between the records of the calling database, each record being provided with an ID corresponding to each ID; Hierarchy database access means for accessing the hierarchy database, and caller data processing means for performing data processing including access to the caller database, wherein the caller data processing means includes a hierarchical database in the hierarchy database access means. Request for access and hierarchical data corresponding to the request Acquiring means, wherein the hierarchical database access means receives a request for access to the hierarchical database from the calling data processing means, accesses the hierarchical database, and passes the result of the access to the calling data processing means It is characterized by being.

Further, the hierarchical data management program storage medium of the present invention which achieves the above object has the following features.
A caller database including a set of records each storing one or more data, each of which has a D, and an ID corresponding to each ID assigned to each record of the caller database. A hierarchical database consisting of a set of records corresponding to the records of the calling database and storing hierarchical data defining the hierarchical relationship between the records of the calling database; and a data process including access to the calling database. Performing caller data processing means, and a hierarchical database access means for accessing the hierarchical database, wherein the caller data processing means requests the hierarchical database access means to access the hierarchical database, and stores hierarchical data corresponding to the request. Having means to obtain
Hierarchical data management, wherein the hierarchical database access means accesses the hierarchical database in response to a request for access to the hierarchical database from the calling data processing means, and passes the result of the access to the calling data processing means. A program is stored.

[0008]

Embodiments of the present invention will be described below. FIG. 1 is a schematic diagram showing an embodiment of the first hierarchical data management system of the present invention. FIG. 1 shows, as an example, an outline of a hierarchical data management system in a case where the first hierarchical data management system of the present invention is applied to an aircraft part development diagram.

That is, as shown in FIG. 1, the hierarchical data management system 1 includes a caller database 100
And a hierarchical database 200 are separately configured. Caller database 100
Are configured as a set of records, each of which stores one or more pieces of data, each of which is provided with an ID (identifier) for identifying each other. That is, as shown in FIG. 1, the caller database 100 has an ID as an item 101, a component name as an item 102, an attribute 1 as an item 103 and thereafter,
A record 111 composed of items such as attribute 2,.
, 112, 113, 114, 115, ... are stored.

The hierarchical database 200 is a record corresponding to a record of the calling database 100 to which each ID assigned to each record of the calling database 100 is assigned.
It is configured as a set of records in which hierarchical data defining a hierarchical relationship between records of 0 is stored. That is, as shown in FIG. 1, records 211, 212, 213, and 21 in the hierarchical database 200 are composed of two items, an ID as an item 201 and a parent ID as an item 202.
4, 215,... Are stored. I of item 201
D is item 1 of each record of the caller database 100
The parent ID of the item 202, together with the ID of the item 201, forms hierarchical data that defines the hierarchical relationship between records in the calling database 100. That is, records 211, 212, 213,
“0” is stored as the parent ID of the record 214, which means that these records 211, 212, 213, 214
Caller database 10 corresponding to the ID assigned to
Each record on the 0 side indicates that there is no upper layer record, that is, no parent record.

On the other hand, "3" is stored as the parent ID of the record 215.
The record 115 of ID: 5 on the side of the calling side database 100 corresponding to the ID: 5 of No.5 indicates that there is a parent record of ID: 3. in this way,
The caller database 100 does not store hierarchical data that defines the hierarchical relationship between records, and the hierarchical data is stored only in the hierarchical database 200.
With such a configuration, in the hierarchical data management system of this embodiment, when the hierarchical relationship between the records stored in the calling database 100 is changed, the maintenance of the calling database 100 is performed. There is no need, and only the maintenance of the hierarchical database 200 is sufficient. Therefore, the quality of the calling side database 100 is prevented from being degraded due to the occurrence of an error that is likely to accompany the maintenance of the database, as compared to the case where the calling side database and the hierarchical database are integrated. In addition, since the database is divided into two, the size of the caller database 100 and the hierarchical database 200 can be reduced, so that the access speed to the database can be improved.

Further, in the hierarchical data management system of the present embodiment, the caller database 100 and the hierarchical database 200 are internally configured as two separate databases, but to the operator as one database. Can be shown. Therefore, when the operator tries to obtain a hierarchical structure diagram using the hierarchical data management system of the present embodiment, an interface with high operability that allows the operator to operate the system as if he / she were accessing one database. It is possible to create

Next, an embodiment of the second hierarchical data management system of the present invention will be described. FIG.
It is a schematic diagram showing one embodiment of the second hierarchical data management system of the present invention. As shown in FIG. 2, the hierarchical data management system 2 includes a calling database 100 and a hierarchical database 200 similar to those shown in FIG. And are provided.

The caller data processing means 300 requests the caller database access means 301 for accessing the caller database 100, and requests the hierarchical database access means 400 to access the hierarchical database 200, and obtains hierarchical data corresponding to the request. And a hierarchical data acquisition unit 302 that performs the operation. Next, the hierarchical database management system of the present invention uses the caller database 100
The operation of each unit until a hierarchical structure diagram is obtained by hierarchically processing records stored in the hierarchical database 200 will be described.

In the hierarchical data management system of the present invention, in order to enhance the versatility of the system, it is desirable to construct the caller database and the hierarchical database as so-called object-oriented databases.
In the following description, an example will be described in which the database is constructed as an object-oriented database in the hierarchical data management system of the present embodiment.

FIG. 3 is a diagram for explaining the operation of hierarchical processing by the hierarchical data management system shown in FIG. In FIG.
An operation explanatory diagram in a case where hierarchical processing is performed using two databases, a caller database and a hierarchical database, is shown. The database of the present embodiment is constructed as an object-oriented database as described above,
The operator can operate as if accessing a virtual database in which the calling database and the hierarchical database are integrated.

Assuming an integrated virtual database corresponding to the two databases as shown in FIG. 1, the operator obtains an entire hierarchical structure diagram by using all data stored in this database. The case where this is attempted will be described below. In this embodiment, the operator can specify the process start component for starting the hierarchical process. However, when the process start component is not specified, an entire hierarchical structure diagram of all components in the database is obtained. Can be

First, when the operator instructs the system to start hierarchical processing without specifying a processing start component, the calling database access means 301 starts accessing the calling database 100, as shown in FIG. To
First, the entity of the calling side database 1: A1 (part name: N
a1) (including attributes 1, 2,...) (step S11).

Next, the hierarchical data acquisition means 302 sends the hierarchical database 20 to the hierarchical database access means 400.
0, and the hierarchical database access means 400 accesses the hierarchical database 200 and
The hierarchical data for me1 is searched to obtain a parent ID = 0, that is, a search result indicating that Name1 has no parent component, and the result is notified to the hierarchical data acquisition means 302 (step S21).

Next, the caller database access means 3
01 accesses the calling side database 100 and acquires data relating to the entity 2: A2 (part name: Name2) of the calling side database (step S12). Next, the hierarchical data acquisition unit 302 requests the hierarchical database access unit 400 to access the hierarchical database 200, and the hierarchical database access unit 400 accesses the hierarchical database 200, searches for hierarchical data for Name2, and ID = 1, that is, Name
2 has a parent part whose ID is 1, ie, Name
A search result of 1 is obtained, and the result is notified to the hierarchical data acquisition means 302 (step S22).

Next, the calling-side data processing means 300 executes the two entities Name1 and N associated with each other.
Based on the search result related to ame2, the hierarchical processing entity 1:
B1 and hierarchical processing entity 2: processing result R for B2
31 and R32, and a hierarchical relationship between these two entities is established (step S30). Thus, records R41 and R42 on the virtual database are obtained (step S40). Name1 is Name2 from these two records R41 and R42 on the virtual database.
You know that you are the parent of

The above hierarchical processing is performed by calling the database 1
By sequentially performing the records stored in 00, the system can grasp the parent-child relationship of the records in the calling database 100, and can provide the entire record to the operator as a hierarchical structure diagram. FIG. 4 is an example of a hierarchical structure diagram created by the hierarchical processing shown in FIG.

FIG. 4 shows a hierarchical structure diagram of parts constituting the aircraft. This hierarchical structure diagram corresponds to the caller database 100 and the hierarchical database 20 shown in FIG.
0 is obtained by the hierarchical processing of the method shown in FIG. 3, and according to the hierarchical structure diagram, for example, ID = 3
It can be seen that the vertical tail of ID = 5 having the tail of the parent as a parent part is a part having a parent-child relationship with each other.

Next, a hierarchical data management program storage medium of the present invention will be described. FIG. 5 is a schematic diagram showing an embodiment of the hierarchical data management program storage medium of the present invention. As shown in FIG. 5, the hierarchical data management program storage medium 500 includes a calling side data processing program 510 corresponding to the calling side data processing means 300 described with reference to FIG. The corresponding hierarchical database access program 520 and the hierarchical database access means are configured to access the hierarchical database in response to a request for access to the hierarchical database from the calling data processing means, and to pass the result of the access to the calling data processing means. Hierarchical data management program 530 and caller database 1
00 and a DB initialization program 540 for initializing the hierarchy database 200 are stored.

The calling-side data processing program 510 includes a calling-side database access program 511 corresponding to the calling-side database access means 301 and a hierarchical data obtaining program 512 corresponding to the hierarchical data obtaining means 302. As a physical medium used for the hierarchical data management program storage medium 500, a portable storage medium such as a CD-ROM, an MO (magneto-optical disk), or an FD (floppy disk), or a stationary storage medium such as a fixed magnetic disk device Storage medium can be used.

Next, a hardware system for operating the hierarchical data management system of the present invention will be described. FIG. 6 is a schematic configuration diagram of a hardware system for operating the hierarchical data management system of the present invention.
FIG. 6 shows, as an example, a DB server 610, a printer server 620, and three clients 630 and 64.
0, 640 are shown connected to each other via a communication line 650. Each of these servers and clients is constituted by a computer system, and includes main units 611, 621, and 63 in which a CPU, a main storage device, an auxiliary storage device, and the like are built.
1, 641, 651, keyboards 612, 622, 632, 6 for inputting various instructions to each computer system
42, 652, and displays 613, 623, 633, and 362 for displaying various screens and providing various information to the operator.
643, 653 and the like.

The main body 611 of the DB server 610 contains a large-capacity auxiliary storage device 614, which is generated by a DBMS (database management system) and built by the hierarchical data management system of the present invention. The caller database and the hierarchical database are stored. Further, the large-capacity auxiliary storage device 614
A caller data processing program corresponding to the caller data processing means including the caller database access means and the hierarchical data acquisition means; a hierarchical database access program corresponding to the hierarchical database access means; A hierarchical data management program configured to access the hierarchical database in response to a request for access to the hierarchical database from the data processing means and to pass the access result to the calling data processing means is stored.

Primarily, each of these software is
Hierarchical data management program storage medium 50 shown in FIG.
0, the hardware system 600
When setting up a hierarchical data management system in
The data is read into the large-capacity auxiliary storage device 614 via the storage medium reading device 615 provided in the main body 611 of the DB server 610.

DB for creating and maintaining caller and hierarchical databases in auxiliary storage 614
Although it is desirable to use an RDBMS (relational database management system) as the MS, it is not necessarily limited to only the RDBMS. The printer server 620 includes a high-speed printer 624.
Are connected, and play a role as a printing device common to the hardware system 600.

[0030]

As described above, according to the present invention,
Since the two databases including the caller database and the hierarchical database are separately configured, it is possible to realize a hierarchical data management system and a hierarchical data management program storage medium with easy database maintenance and high access speed.

[Brief description of the drawings]

FIG. 1 is a schematic diagram showing an embodiment of a first hierarchical data management system of the present invention.

FIG. 2 is a schematic diagram showing an embodiment of a second hierarchical data management system of the present invention.

FIG. 3 is an explanatory diagram of an operation of hierarchical processing by the hierarchical data management system shown in FIG. 2;

FIG. 4 is an example of a hierarchical structure diagram created by the hierarchical processing method shown in FIG. 3;

FIG. 5 is a schematic diagram showing an embodiment of a hierarchical data management program storage medium of the present invention.

FIG. 6 is a schematic configuration diagram of a hardware system for operating the hierarchical data management system of the present invention.

[Explanation of symbols]

1 Hierarchical data management system 100 Calling side database 101, 102, 103 Items 111, 112, 113, 114, 115, ...
Record 200 Hierarchical database 201, 202 Items 211, 212, 213, 214, 215, ...
Record 300 caller data processing means 301 caller database access means 302 hierarchical data acquisition means 400 hierarchical database access means 500 hierarchical data management program storage medium 510 caller data processing program 511 caller database access program 512 hierarchical data acquisition program 520 hierarchy Database access program 530 Hierarchical data management program 540 DB initialization program 600 Hardware system 610 DB server 620 Printer server 630, 640, 650 Client 650 Communication line 611, 621, 631, 641, 651 Main unit 612, 622, 632 642,652 Keyboard 613,623,633,643,653 Display 614 Storage device 615 storage medium reading device 624 printer

Claims (3)

[Claims] 1. A hierarchical data management system having a database for managing hierarchical data, comprising a set of records each having at least one data stored therein, each of which has an ID for identifying each other. Caller database, and each ID given to each record of the caller database
A hierarchical database comprising a set of records in which hierarchical data defining the hierarchical relationship between the records of the calling database, the records being records corresponding to the records of the calling database, each having an ID corresponding to A hierarchical data management system characterized in that two databases are separately configured. 2. A caller database comprising a set of records each storing one or more data, each of which is provided with an ID for identifying each other, and each ID attached to each record of said caller database. A hierarchical database comprising a set of records each having a corresponding ID and corresponding to a record of the calling database and storing hierarchical data defining a hierarchical relationship between the records of the calling database; Caller data processing means for performing data processing including access to the caller database, and hierarchical database access means for accessing the hierarchical database, the caller data processing means, the hierarchical database access means of the hierarchical database Means for requesting access and obtaining hierarchical data corresponding to the request The hierarchical database access means receives the request for access to the hierarchical database from the calling data processing means, accesses the hierarchical database, and passes the result of the access to the calling data processing means. A hierarchical data management system characterized by the following. 3. A caller database comprising a set of records each storing one or more data, each of which is provided with an ID for identifying each other, and each ID given to each record of said caller database. A hierarchical database comprising a set of records each having a corresponding ID and corresponding to a record of the calling database and storing hierarchical data defining a hierarchical relationship between the records of the calling database; Caller data processing means for performing data processing including access to the caller database; and hierarchical database access means for accessing the hierarchical database, wherein the caller data processing means accesses the hierarchical database access means to access the hierarchical database. And means for acquiring hierarchical data corresponding to the request. The hierarchical database access means receives the request for access to the hierarchical database from the calling data processing means, accesses the hierarchical database, and passes the result of the access to the calling data processing means. A storage medium for a hierarchical data management program, wherein a hierarchical data management program is stored.