JPH04319744A - Management system for partial set of objects in data base - Google Patents

Abstract

PURPOSE:To manage the objects of a partial set by a normal mode storage format in respect to the management system of the partial set of objects in a data base. CONSTITUTION:A data base management system for managing plural objects formed by a single object structure having each identifier(ID) and plural attributes by a table format in each class is provided with a partial set managing table (2) having structure provided with an object ID(OID) for identifying a partial set and the set(SET) of partial set ID group corresponding to the OID, at the time of accessing the partial set of objects in a certain class, the partial set managing table (2) is pointed out by a detail attribute PROP having a single object structure, an object concerned is pointed out by the set(SET) of the table (2) and the single object and the objects in the partial set are managed by the same management format having the OID.

Description

[Detailed description of the invention]

0001

[Industrial Application Field] The present invention stores a plurality of objects having a single object structure, each having an identifier (OID) and a plurality of attributes (PROP), in a table format with classes (A, B, C, -) This relates to a method for managing a subset of objects of a certain class (B) in a separately managed database management method.

[0002] Conventional databases were mainly constructed for general office processing, and rarely handled subsets of a certain database. However, recent advances in the design and manufacturing fields, such as computer-aided design (CAD),
, Computer Aided Manufacturing (CAM) With advances in technology, design data and manufacturing data are increasingly being managed as databases in this field.

[0003] In this case, the structure of the database often takes a hierarchical structure such as, for example, device → unit → package → integrated circuit, and when accessing the database, the database at a certain level, for example, It has become necessary to handle a subset of package design data (design data for multiple specific integrated circuits).

[0004] The database stores a plurality of objects having a single object structure having an identifier (OID) and a plurality of attributes (PROP) in a class (A) in the form of a table.
, B, C, ~) If you use a separate management format (called normal form), when you try to handle the above subset, one attribute can have multiple values (corresponding to the number of elements in the subset), i.e. , it is necessary to prepare a so-called non-normal table that has multiple identifiers (OIDs) of the subset, which may complicate the processing. , a database management method that can effectively handle this is needed.

[0005]

2. Description of the Related Art FIG. 2 is a diagram illustrating a conventional method for managing a subset of objects. In this figure, (b)
, (c) is a class (A
, B, C, ~) indicates a form that is managed separately (referred to as normal form).

[0006] When objects (b1, b2, b3) and objects (b5, b6) of such a single object management table (■) are treated as subsets, as shown in FIG. As shown, one attribute (PROP1) 11 of the table (2) has a structure that handles multiple values, that is, multiple identifiers (b1, b1,
b2, b3, and b5, b6), the so-called
A non-normal object management table ■ was being constructed.

[0007]

[Problem to be Solved by the Invention] This is because if a subset of the object is stored as normal form data, there is a problem that performance will deteriorate in terms of memory efficiency and access efficiency. On the other hand, since the single object management table ■ and the collection of objects 1 are handled differently, processing becomes complicated and difficult to handle.

Specifically, there was a problem in that a subset of object 1 could not be treated as an object. Furthermore, in the storage format of the subset of object 1 shown in Figure 2, even if the form of the subset seen from a certain user can be recognized, it is difficult to know what kind of subset the same object is treated by other users. There is a problem in that it is difficult to recognize whether the subset is correct, and access to the subset becomes complicated.

In view of the above-mentioned conventional drawbacks, the present invention provides a method for managing a subset of objects in a database.
By representing a subset of objects as an element with an object identifier (OID), that is, an object, in the same way as a single object, a single object and a set of objects can be treated the same. The objective is to provide a method for managing subsets of objects in a database that allows for

0010

[Means for Solving the Problems] FIG. 1 is a diagram showing one embodiment of the present invention. The above problems are solved by a database management system configured as follows.

[0011] In each case, an identifier (OID) 1
0 and multiple attributes (PROP) 11 This is a database management method that manages a plurality of objects 1 having a single object structure in a table format for each class (A, B, C, ~), and a certain class ( B) To manage a subset of object 1, an identifier (OID) 20 that identifies the subset, and the identifier (OID)
Identifier group (SET) of subset corresponding to 20 Subset management table with structure where 21 is object 2 ■
When accessing a subset of objects (b1, b2, b3, ...) of a certain class (B), the attribute (PROP
) 11, point to the subset management table ■ and select the set of identifiers (SE
T) At 21, point to object 1 of the relevant class (B), and identify the single object 1 and the subset object 2 by their object identifiers (OIDs).
10, 20 and attribute (PROP) 11, or
It is configured to be managed using the same management form consisting of SET 21.

0012

[Operation] That is, in the present invention, in each case,
Identifier (OID) 10 and multiple attributes (PROP)
11 Multiple objects 1 of a single object structure with classes (A, B, C, ~
) In a database management method that manages separately, for example, a subset of object 1 of class B (b1, b
2, b3), etc., a structure similar to that of a single object, that is, an identifier (OID) 20 and an attribute (P
A subset management table ■ with a set (SET) 21 is provided instead of ROP) 11, and from a single object 1 of class A that indicates a subset of a certain class, for example, a database, the subset management table ■ is provided. , the attribute 11 of the single object 1 is the identifier (O
ID) 20, the objects of the subset can be accessed.

Therefore, in the object 1 of class A that accesses the subset management table (2), conventionally, the attribute 11 of the object 1 has a plurality of identifiers of the object 1 of the subset as attribute values. In the database management method of the present invention, what is required to be in a so-called non-normal form can be made into a normal form database, which is a normal object management table. By doing so, the same object (b1, b2, b3, etc.)
By referring to each subset management table (■), it is possible to recognize what kind of subset the user is treated as by other users. Also, a single object management table■
Since the subset management table (1) has the same structure, an effect can be obtained in that operations on a single object and operations on the set object can be made the same.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Examples of the present invention will be described below in detail with reference to the drawings. FIG. 1 described above is a diagram showing an embodiment of the present invention.

In the present invention, each has an identifier (OID) 10 and a plurality of attributes (PROP) 11.
Multiple objects 1 of a single object structure with a class (A, B, C, ~) in table form.
In a separately managed database management method, for example,
Class B object 1 subset (b1, b2,
b3) etc., a structure similar to that of a single object is used, that is, an identifier (OID) 20 and an attribute (PRO
P) Instead of 11, the set of identifiers of the subset (
SET) A subset management table ■ with 21 is provided, and each single object management table ■ has attributes 11
From, the identifier (OID) 2 of the subset management table ■
The means to point to 0 is the means necessary to implement the invention. Note that the same reference numerals indicate the same objects throughout the figures.

The configuration and operation of the database object subset management system according to the present invention will be explained below with reference to FIG. First, the database related to the present invention is shown in Figure 1.
As shown in the object management table for class B and class C of Classes (A, B, C,
~) are managed separately.

[0017] For example, when managing a subset of objects consisting of objects b1, b2, and b3 of class B, in the present invention, an identifier (OID) having a structure similar to that of the single object management table
20 and the set (
SET) 21 is provided, and identifiers b1, b2, b3 of the subset are set in the SET 21 column.

With this configuration, the single object management table ■ and the subset management table ■ have object identifiers (OIDs) 10 and 2, respectively.
0, and the operations on the single object management table ■ and the operations on the subset management table ■ can be the same, and each single object management table ■ can refer to objects in the subset. Even if the attributes of each object 1 (PROP
) 11, it is no longer necessary to set multiple values {specifically, the object identifier (OID) 20 of the subset}, and simply set the identifier (OID) of the subset management table
ID) 20 points is sufficient, and the corresponding class A
The object management table ■ can be a normal normal form database.

In the example shown in FIG. 1, a subset of the database is designated by class A, and the identifier (OID) of the subset management table is specified in attribute (PORP1) 11 of the single object management table (■) of class A. For example, by setting "a22s" and searching the identifier (OID) column of the subset management table ■,
Extract the corresponding identifier “a22s” and create its set (SET
) Referring to column 21, identify the object identifiers b1, b2, b3 of the subset having the identifier "a22s".
can be recognized and objects having the identifiers b1, b2, b3 can be extracted.

Note that the attribute (PORP2) 11 of the single object management table (3) of class A specifies only the normal objects C4 and C6, so the display format is the same as before.

[0021] In this way, the database management method of the present invention expresses a set of objects as an element having an identifier (OID) in the same way as a single object, thereby distinguishing between a single object and a set of objects. of,
The feature is that it can be handled in the same way.

[0022]

Effects of the Invention As explained in detail above, the database object management method of the present invention has an identifier (OID) and a plurality of attributes (PROP).
) is a database management method in which multiple objects with a single object structure are managed by class using a single object management table. Identifier (OID) and the identifier (OID)
When accessing a subset of an object of a certain class by providing a subset management table ■ with a structure that includes a set (SET) of subset identifiers corresponding to , point to the corresponding identifier (OID) in the above subset management table ■, and use the set of identifiers (SET) in the subset management table ■ to select the identifier (OID) of the corresponding object.
), and connect the single object and the subset object to an object identifier (OID), an attribute, or a set (SET).
This has the effect that operations on a single object and operations on a subset of objects can be handled in a unified manner.

[Brief explanation of the drawing]

[Fig. 1] A diagram showing one embodiment of the present invention.

[Figure 2] Diagram explaining the conventional management method for object subsets

[Explanation of symbols]

1 Object of single object management table, 10 Identifier (OID) or object identifier (OID) 11 Attribute (PROP) 2 Object of subset management table 20
Identifier (OID) or object identifier (OID) 21 Set (SET) ■ Single object management table or table ■ Subset management table

Claims (1)

[Claims] Claim 1: In each case, an object identifier (
OID) (10) and multiple attributes (PROP) (11)
) with multiple objects (1) of a single object structure in the form of a table (■) with classes (A, B,
C, ~) is a database management method that manages a subset of objects (1) of a certain class (B) using an identifier (O) that identifies the subset.
ID) (20) and a set (SET) of a subset of identifiers corresponding to the identifier (OID) (20) (21)
A subset management table (■) with a structure where object (2) is provided, and when accessing a subset (b1, b2, b3, ...) of objects of a certain class (B), the above single object structure is table
Point the above subset management table (■) in the attribute (PORP) (11) of (■), and set the identifier group set (SET) (21) of the subset management table (■).
, the object (1) of the class (B) is pointed to, and the single object and the objects of the subset are identified by object identifiers (OIDs).
(10, 20); and an attribute (PROP) (11) or a set (SET) (21).