JPH01276334A - Data base - Google Patents

Abstract

PURPOSE:To handle the multi-medium data that could not be handled with a relational data base by preparing a link defining area to store the key value of the multi-medium data and at the same time securing the linkage between said defining area and the multi-medium data to take out the contents of said data. CONSTITUTION:The field value (key value) is controlled by a key value control part 2 and stored in a data base file device 5. While the object data on the data pool area linked with the key value are stored in the data pool devices 6 and 7 and controlled by an object control part 3. Then the linkage between said key value and the object data is controlled by a link control part 4. In other words, such data pool areas are set at various memory media like a compact disk, an optical disk, etc., and therefore various object multiple media can be handled via various physical memory multiple media.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of Industrial Application The present invention relates to a database device based on a relational model.

Conventional technology Relational databases (relational database management systems) express data and data structures using normalized indivisible data sets and constraints on the sets. Therefore, by making Nukima public, it is possible to easily convey the data structure to others, making it extremely versatile.

In addition, certain operations (relational operations) are prepared for data and data sets, making it an excellent data model that allows you to easily extract data and change the data structure. For this reason, relational databases are widely used in the field of office processing, where there is a lot of data that has a relatively simple structure and is easy to normalize.

Problems to be Solved by the Invention For the reasons mentioned in the prior art section, relational databases have been adapted for routine applications in the field of business processing. However, recently, there has been an increase in the number of cases in which large amounts of data are used for general purposes by multiple people outside of the field of administrative processing.In this case, the nature of the data is not limited to numeric data or fixed-length character data as is the case with administrative data. It becomes necessary to handle many types of data, such as variable-length character data, graphic data, sound data, natural image data, and video data.

Furthermore, due to the nature of these data, various types of data storage media are required, such as not only floppy disks and hard drives, but also compact disks and optical disks.

A thousand hands of offshore multimedia.

The demand for handling various physical storage multimedia is high.
It's coming.

This so-called multimedia data has a problem in that conventional 1) relational databases cannot practically handle it due to the strong restriction of normalized data.

In view of this problem, the present invention attempts to handle the above object multimedia and physical storage multimedia while retaining the excellent versatility of relational databases.

Means for Solving the Problems In order to solve the above-mentioned problems of conventional relational databases, the present invention provides a data pool area in which each field value of a pre-specified definition area is separately defined in a relational database. a link management unit that links to the data of , a representative value management unit that extracts each field value for the specified domain, and a data file that links to each field value for the specified domain described in -.

- The relational database is expanded to include an object management section that retrieves data from the file area.

According to the above-described configuration, the present invention stores variable-length character data, graphic data, sound data, natural image data, video data, etc. in a separately defined data pool area, and furthermore, stores variable length character data, graphic data, sound data, natural image data, video data, etc. By setting the object multimedia to various storage media such as compact discs and optical discs as well as hard drives, it is possible to handle various object multimedia with various physical storage multimedia. At this time, each multimedia data is linked to each field in a prespecified domain of the relational database, and the data in each field acts as a representative value of the linked multimedia data. This link domain extended by the present invention is not subject to conventional relational operations, but the selection of tuples is performed by conventional relational operations on other fields of the tuple containing this domain, resulting in a link domain field value is extracted as a representative value of multimedia data, or linked multimedia data is directly extracted.

By creating a new link domain to store representative values of multimedia data, we have created a new link domain that stores representative values of multimedia data. This makes it possible to handle empty full 4-media data.

Embodiment Hereinafter, a database apparatus according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 shows a configuration diagram of a database device in an embodiment of the present invention.

In FIG. 1, 1 is an input/output and arithmetic processing unit, 2 is a representative value management unit, 3 is an object management unit, 4 is a link management unit, 5 is a database file device, 6 is a data pool device A, and 7 is data pool device B.

The operation of the database device configured as described above will be described below with reference to FIGS. 1 and 2.

FIG. 2 shows an example in which graphic data, which could not be handled in the past, is handled at the same time as character and numerical data, which can be handled in a conventional relational database. In FIG. 2, the attributes of "name" and "color" are stored in the database file device 6 in the same way as in the conventional relational database, and the input and arithmetic processing unit 1 performs the conventional calculations. administered. On the other hand, the attribute "picture" is an attribute expanded by the present invention (Tights Buying Type) and is directly field-directed (representative value) such as 1 picture of an apple, 1 "picture of an orange," and 1 "picture of a banana." is managed by the representative value management section 2 and stored in the database file device 5.

The object data in the data pool area linked to this representative value is stored in the data pool device 6.7 and managed by the object management section 3. Typical values and objects) - data links are linked by link management section 4
will be managed accordingly.

The data creation method will be described using the "apple picture" shown in Figure 2 as an example. Amazumi creates a picture of an apple on data pool device A. This creation tool may be prepared as a utility for the database device, or may be completely separate software.

However, the data structure can be controlled by the object management section 3. Regarding this point, there are two methods: adopting a data structure close to the standard such as PO3TSCRIPT and providing this data structure control section in the object management section 3; One possible method is to transfer control to each control software only during structural control. In either case, the object created in the data pool device (in this case, a picture of an apple) can be retrieved from the object management unit 3 under the name "Picture of an apple". Note that although this example shows a graphic, various types of objects can be considered, including moving images and audio.

Next, the user uses the input/output and arithmetic processing section 1 to create a relational table having "name" and "color" as attributes, similar to a conventional relational database.

After that, similarly, in the input/output and arithmetic processing unit 1, define the attribute of the link attribute "Picture".Then, when this field value "Picture of rindo" is input, "Picture of rindo"
Gives instructions to link with the object.

In accordance with this instruction, the link management section 4 (/i link property field' value and object name 1 managed by the object management section 3) 11 is linked. The representative value management unit 2 stores and retrieves link attribute field values from the database file device 5, but this function may be replaced by conventional calculations in the input/output and calculation processing unit 1. . However, it is assumed that relational operations cannot be performed on link attributes.

Next, a method for making inquiries about the data created as described above will be described. In FIG. 2, since the link attribute "picture" cannot be subjected to the rotational operation 1'&IJ, an inquiry is made to other attributes. For example, if you give an instruction to show a ``name'' and 1 picture whose ``color'' is ``red,'' the input/output and arithmetic processing unit 1 will search for a tuple whose ``name 11'' is 1 apple, ”. Next, in response to an instruction from the input/output and arithmetic processing section 1, the representative value management section 2 removes the field value "picture of an apple" from the "picture" of the same tuple.

Next, the link management section 4 extracts the object l-name "apple picture" linked to "apple picture" through the object management section 3, and returns the object "apple picture" to the user.

In the above explanation, the field value of the link attribute and the object name are both "picture of an apple", but this does not necessarily have to be the case. The link correspondence between the field value of the link attribute and the object name is managed by the link management unit 4.

Also, in Figure 2, the "picture of apples" and "picture of oranges" are stored in data pool device A, and the "picture of banana" is stored in data pool device B, but as in this example, It also allows objects to be stored on multiple devices. This is because different objects 1- may be stored on different physical media. First, use a compact computer for large amounts of code data, and an optical disk for videos.
This is because it is considered appropriate for codes that require high-speed access to be coded using hard disk drives. In FIG. 1, the database file device 5 and data pool devices A and B may be physically the same media.

Effects of the Invention As described above, the present invention provides a link management unit that links each field value in a prespecified domain with data in a separately defined data spool area in a relational database, and a Equipped with a representative value management section that extracts each field value, and an object management section that extracts the data in the data pool area linked to each field value for the specified domain, Tony has developed various object multipliers. It becomes possible to handle media as various physical storage multimedia. At this time, conventional relational calculations can be performed on attributes other than link attributes, so the above multimedia support is possible without sacrificing the versatility that is a major feature of relational databases.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a configuration diagram of a database device according to an embodiment of the present invention, and FIG. 2 is an explanatory diagram showing the handling of graphic data according to the present invention. 1 - Human output and arithmetic processing section, 2- Representative value management section,
3. Object management section, 4. Link management section,
5 ・Database file device M, 6 data pool device person, end...Data pool device B.

Claims (2)

[Claims] (1) A link management unit that links each field value of a pre-specified domain with data in a separately defined data pool area, a representative value management unit that extracts each field value from the above-specified domain, and the above-mentioned 1. An object management unit for extracting data from a data pool area linked to each field value for a specified domain. (2) A means for linking each field value in a pre-specified domain with data in a separately defined data pool area, a means for extracting each field value from the above-specified domain, and a means for extracting each field value from the above-specified domain. A database device comprising: means for extracting data from a data pool area linked to each field value.