JPH04246773A - Data base managing system - Google Patents

Abstract

PURPOSE:To constitute the system so that hierarchical information between blocks can be extracted automatically by an access control part, and the extracted hierarchical information can be managed. CONSTITUTION:A data base managing system 1 reads in a structure definition of user data from a meta-data base 15 at the time of actuation of an application program, and holds it in a meta-data table 9 in a meta-data control part 8. When store of data is started, a management data operating part 4 reads in a management data file 13 through a management data access part 10 and determines a store position of the target user data. A data operating part 6 writes in the user data to a data base 14 through a data base access part 11, while referring to information of the meta-data table 9. In this case, when modified information extraction data exists in meta-data, a hierarchical information extracting part 7 generates a request of hierarchical information store to a hierarchical information store part. The hierarchical information store part 5 writes hierarchical information in the management data file 13.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database management system, and more particularly to a database management system for an LSICAD system.

0002

[Background Art] Conventionally, in this type of database management system, data access when storing and managing design data is performed in units of blocks to be processed, and management within management data files is also performed in units of blocks. .

0003

In the conventional database management system described above, data management is performed independently on a block-by-block basis, so there is a drawback that hierarchical information between blocks cannot be managed.

0004

[Means for Solving the Problems] A database management system of the present invention includes a database in which design data at the time of LSI design is stored, a metadatabase in which structure definition data of user data in the database is stored, and a metadatabase in the database. In a database management system consisting of a management data file that stores the version number and storage location of user data, and an access control unit that reads data structure definition data in the metadata database and accesses the user data according to the data structure definition, The database stores data in management units, the metadatabase stores the data structure definition data and hierarchy information extraction data, the management data file stores the version number, storage location, and hierarchy information, and the access control The section reads the data structure definition data and the hierarchy extraction data, accesses the design data in accordance with the data, and includes a section for extracting hierarchy information in the design data.

[0005]

Embodiments Examples of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram of the database management system of the present invention. The database management system 1 reads the structure definition of user data from the metadata database 15 when an application program is started, and stores it in the metadata table 9 in the metadata control unit 8 for future access. When data storage is started, the management data operation unit 4 reads the management data file 13 through the management data access unit 10 and determines the storage location of the target user data.

When writing user data, the data operation unit 6 writes the user data to the database 14 through the database access unit 11 while referring to information in the metadata table 9 shown in FIG. At this time, if modification information extraction data exists in the metadata, the hierarchical information extracting unit 7 determines the lower block name and issues a request to the hierarchical information storage unit to store the hierarchical information. The hierarchical information storage unit 5 writes hierarchical information to the management data file 13 through the management data access unit.

FIG. 2 is a configuration diagram for explaining metadata of the present invention. The table information table 16 has information on a user data table. The table information table 16 has a table name, a number added to the table, a hierarchy flag indicating the existence of data for hierarchy extraction, and a pointer to the item information table. Item information table 1
7 has information about each item in the table. The item information table 17 has information about each item in the table. The item information table 17 has item name, item type, item size, and hierarchy flag. Here, if the hierarchy flag is ON, it means that the data corresponding to this item indicates the name of a lower block.

FIG. 3 is a configuration diagram for explaining the management data of the present invention. The block name table 18 is a list of information stored in the database, and has a block name, version number, storage location, and hierarchical table pointer. The hierarchy table 19 is pointed to from the block name table, and has the block names and version numbers of blocks located in the lower hierarchy.

FIG. 4 is a flowchart for explaining the operation of the access control section of the present invention. When there is a request to write user data, a one-record write process 20 operates, and then the process moves to a storage table search process 21. After searching the storage table, the process moves to table attribute check 22. If the table does not have a hierarchy flag, the process immediately moves to the database access unit 26. If the table has a hierarchy flag in the table attribute check 22, the process moves to the item count repetition process 23.

Thereafter, the hierarchy flag check 24 is performed for the number of items, and if the hierarchy flag is ON, the process moves to the hierarchy information addition process 25. In the hierarchy flag check 24, if the hierarchy flag is OFF, the process moves to the next item without doing anything. When the item count repetition process 23 is completed for all items, the process moves to the database access unit 26.

Next, the operation of the database management system of the present invention will be explained using a specific example. As shown in Figure 2, there is one type of table "COMP", and its items are "CELL", "NAME", "X" and "Y", and if the hierarchy flag is ON for item "NAME". do. At this time, consider the case where design data with the name "BLOCK-A" is stored.

When a record with item "NAME" as "BLOCK-B" is given to the "COMP" table as data to be written, the hierarchy flag check 24 determines that "BLOCK-B" is written according to the flow shown in FIG.
is passed to hierarchical information addition processing. In the hierarchical information addition process,
Add “BLOCK-B” to the hierarchy table. next"
The item “NAME” is “BLC” in the “COMP” table.
When the record of "CK-C" is given, the record of "BLOCK-C" is added to the hierarchy table through similar processing, and management data as shown in FIG. 3 is generated.

[0013]

[Effects of the Invention] As explained above, the present invention has the advantage that hierarchical information between blocks can be automatically extracted within the access control unit and the extracted hierarchical information can be managed in a database management system that stores design data. There is.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a diagram showing the structure of metadata of the present invention.

FIG. 3 is a diagram showing the structure of management data of the present invention.

FIG. 4 is a flowchart showing the operation of access control according to the present invention.

[Explanation of symbols]

1 Database management system 2 Application interface 3
Access control section 4 Management data operation section 5 Hierarchical information storage section 6 Data operation section 7 Hierarchical information extraction section 8 Metadata control section 9 Metadata table 10 Management data access section 11 Database access section 12 Metadatabase access section 13
Management data file 14 Database 15 Metadatabase 16 Table information table 17 Item information table 18 Block name table 19 Hierarchy table 20 1 record write start process 21
Storage table search process 22 Table attribute check 23 Item count repetition process 24 Hierarchy flag check 25 Hierarchy information addition process

Claims (1)

[Claims] Claim 1: A database that stores design data during LSI design, a metadatabase that stores structure definition data of user data in the database, and stores the version number and storage location of the user data in the database. In a database management system comprising a management data file and an access control unit that reads data structure definition data in the metadata base and accesses user data according to the data structure definition, the database stores data in units of management. , the metadatabase stores the data structure definition data and the hierarchy information extraction data, the management data file stores the version number, storage location, and hierarchy information, and the access control unit stores the data structure definition data and the hierarchy extraction data. 1. A database management system comprising a section for reading data and accessing design data in accordance with the data, and extracting hierarchical information within the design data.