JP2002196959A - Database management and device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a database management method and a device capable of managing not only a standard data type but also a newly-defined optional data type with a database to a conventional system for managing only the standard data type and executing data operation corresponding to the standard data type, and executing operation extension to an organized database. SOLUTION: This management is attained by installing a first means for housing an inputted data type, and a second means for executing interface extension of the database management system so as to correspond to the data type definition of the data type when the data type is housed by the first means.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to computer data management, and more particularly, to a function expansion method for a database management system suitable for multimedia database management.

[0002]

2. Description of the Related Art A conventional database management system is based on the standard data of the system, as described in Chapter 4 of the document "Relational Database Management System", the creation and internal structure of a relational database (Takayuki Hirao, Modern Science). Only types (characters and numerical values) are managed, and data operations are performed in accordance with this standard data type.

[0003]

In the above prior art, the data type of multimedia data such as image data cannot be stored and managed in the database, and the multimedia data type is stored in the database as another attribute. Even if it can be stored, it cannot perform operations on multimedia data types as a database management system.

Therefore, when creating a multimedia database using a conventional database management system,
Since the recognition and operation of the data structure are left to the UAP (user application program), the database managed by the database management system is a UAP dedicated file.

[0005] It is an object of the present invention to provide a database management method and apparatus capable of managing multimedia data types and performing such operations, and using a database for many UAPs.

[0006]

[Means for Solving the Problems]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is an overall configuration diagram of a database management system according to the function extension system of the present invention.

The database management system 1 includes a DB access interface control unit 2 and an interface extension mechanism 3, and further includes a language-specific preprocessor 6, a language-specific include file 7, and an extension function library 8.
The language-specific include file 7 stores a data type for each language and a data type definition corresponding to this data type. Further, the catalog has an extended data type management table 4 and an extended data operation management table 5 as a catalog.

[0009] The DB access interface control unit 2
A component that analyzes requests from end users and UAPs and controls access to the database based on the requests. The interface extension mechanism 3 is a subcomponent of the DB access interface control unit 2 having a function of extending the DB access interface by a command (data type definition command, data type operation registration command) newly added in the present invention. The extended data type management table 4 manages a data type defined by a user. The extended data type operation management table 5
It manages data operations defined by the user. The language-specific include file 7 is a file that stores user-defined data types and data type definitions for each language, and is an input to the language-specific preprocessor 6. The extension function library 8 is a library for storing a load module for a data operation defined by a user.

Next, the operation of the database management system 1 when a user defines a new data type will be described with reference to FIGS. 1, 4 and 5.

In the present invention, in order to define a data type,
A data type definition command 15 as shown in FIG. 4 is provided.
By inputting this data type definition command 15,
An extended data type management table 4 is generated.

FIG. 5 is a flowchart showing processing after command analysis. The DB access interface control unit 2 analyzes the extended data type definition command 15 and registers the data type in the extended data type management table 4 (step 16). FIG. 2 shows an example of the configuration of the extended data type management table 4. The extended data type management table 4 includes a language type,
It consists of a data type name, data type definition, and definition file name. Returning to FIGS. 1 and 5, the language-specific include file 7 is updated according to the language type (step 1).
7). Finally, the DB access interface control unit 2 is extended by the interface extension mechanism 3 (step 1).
8). Thereby, for example, when the user accesses the database, the DB access interface control unit 2 searches the extended data type management table 4 based on the command input by the user, and if the extended data type management table 4 exists in the extended data type management table 4, By registering the data type, the command for allowing the user to access the database can be extended. Further, data can be read from or written to the database according to the definition corresponding to the data type input when the user accesses the database.

Next, an example of the operation of the database management system 1 when a user registers a new data operation will be described with reference to FIGS. 1, 6, and 7. FIG.

In the present invention, an extended data operation registration command 25 as shown in FIG. 6 is provided to register a data operation. By inputting the extended data operation registration command 25, the extended data operation management table 5 is generated. The DB access interface control unit 2 analyzes the extended data operation registration command 25 and registers information indicating the location where the data type operation is stored in the extended data operation management table 5 (step 26). An example of the extended data operation management table 5 is shown in FIG. The extended data operation management table 5 includes an operation type, a language type, an operation interface, and a file name indicating a location where a data operation is stored. Returning to FIG. 1 and FIG. 7, further, a data operation load module described by the user based on the file name is registered in the extended function library 8 managed by the database management system 1 from the user-created library 23 owned by the user. (Step 27). Finally, the DB access interface control unit 2 is extended by the interface extension mechanism 3 (step 28, step 2).
9).

Next, the process of creating a load module from a UAP source program using the extended data type and data operation will be described with reference to FIG.

The UAP source program 31 describing the data type and the data type definition corresponding to this data type in the language-specific include file 7 are stored in the language-specific preprocessor 6.
To enter. As a result, the language-specific preprocessor 6 expands the data type so that it can be input to the compiler. Further, the expanded version is input to the compiler 30, and
When the output from the compiler 30 and the load module for data manipulation stored in the extension function library 8 are input to the linkage editor 40, the UAP load module 32 is output. Here, the compiler 30
Is for converting a UAP source program into load modules, and the linkage editor 40 is for linking and editing a plurality of load modules.

A UAP is created by the above processing.
As described above, since the data type definition in the language-specific include file 7 corresponding to the data type in the UAP source program 31 can be used, the creator does not need to define the data type when creating the UAP source program 31. . Further, as the data operation related to the data type is registered, the available data operation increases when the load module is created.

Next, an operation example of the database management system 1 by issuing a command including an extended data type and a data operation will be described with reference to FIG. Since all the command operations are incorporated in the database management system 1, the input / output operation of the extended data type and the extended data operation are executed by this request (34, 35). On the other hand, the extended function 33 other than the command operation is
0 is incorporated in the UAP. Therefore, the function incorporated is executed by the request 36 for the extended function.

Further, as shown in FIG. 10, an extended data type list display command 37 and an extended data operation list display command 38 may be defined and input so that the extended data type or data operation can be easily used. The contents of the extended data type management table 4 are displayed by the extended data type list display command 37. Also, the extended data operation management table 5 is displayed by the extended data operation list display command 38.
Display the contents of

[0020]

According to the present invention, any data type other than the standard data type can be managed in the database, the operation can be extended to the constructed database, and the diversity of the multimedia database can be handled. effective.

[0021]

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram of a database management system according to an embodiment of the present invention.

FIG. 2 is an example of an extended data type management table.

FIG. 3 is an example of an extended data operation management table.

FIG. 4 is a diagram showing an extended data type definition command format.

FIG. 5 is a flowchart showing the operation of the database management system when defining an extended data type.

FIG. 6 is a diagram showing a format of an extended data operation registration command.

FIG. 7 is a flowchart showing the operation of the database management system when defining a data type.

FIG. 8 is an operation conceptual diagram when a UAP is created.

FIG. 9 is a conceptual diagram of the operation of a database management system and a UAP according to a UAP or a user request.

FIG. 10 is a conceptual diagram of the operation of the database management system when an extended data type / extended data operation list display request is issued.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Database management system, 2 ... DB access interface control part, 3 ... Interface extension mechanism, 4 ...
Extended data type management table, 5: Extended data operation management table, 6: Preprocessor by language, 7: Include file by language, 8: Extended function library, 9: Database.

Claims (4)

[Claims] 1. A command for defining an extended data type is received upon receiving a request to specify a data type definition composed of a name of a data type to be extended, a language type, and a standard data type provided by the system. And database management method. 2. A parameter including an operation file name indicating a data operation type to be extended, a language type, a location where the data operation is stored, a name of the data operation to be extended, and an extended data type used in calling those operations. A database management method comprising: specifying an operation interface composed of the following data types; and executing a command for registering and defining an extended data operation. 3. The database management method according to claim 1, wherein the language type is FORTRA.
A database management method comprising specifying N languages. 4. The database management method according to claim 2, wherein said extended data type is a multimedia data type composed of image data.