JPH0895996A - Database - Google Patents

Abstract

PURPOSE: To enable a database to be easily utilized at a high level for such as the addition of a new data format. CONSTITUTION: An object-oriented database managing system 1 is utilized for constructing a database 2 and the object-oriented database managing system 1 is provided with a function for defining a class corresponding to the basic data format and describing a data retrieval method and a data display method concerning the data format, function for describing the method to analyze/ execute the retrieving expression concerning the class and the method to analyze/execute display layout by defining the class consisting of one record by surrounding arbitrary number of objects, and GUI function for integrating the data format defined by a user, class corresponding to this data format and the data retrieval method and data display method of that class, selecting the data constitution of the record on a screen together with a previously integrated data format and designing the display layout.

Description

Detailed Description of the Invention

[0001]

The present invention relates to a database,
Especially object-oriented database management system (OO
A database using a DBMS).

[0002]

2. Description of the Related Art Most of the databases currently in practical use are relational database management systems (RD).
BMS).

That is, RD is used to build a database.
Except when developing from BMS itself, generally, a commercially available RDBMS is purchased, and a user (or a database developer) builds a database using the database building means provided by the RDBMS.

The database construction means has a structure of one record stored in the database, for example, by sequentially embedding data names and types in an empty table displayed on a computer screen as necessary. There are ways to define it.

The RDBMS is prepared in advance with several data types (character string, numerical value, etc.), and the user selects an appropriate one from them, but the user adds a new data type. It is not possible.

[0006]

Although the conventional database construction means is a simple means for a user to construct a database, it is necessary to add a new data type or implement a new data search means. This makes it difficult to use the database at a high level.

For example, a conventional RD is used for constructing a database for acquisition, storage, retrieval, display, reuse, etc. of various products that can be stored in a storage device of voices, moving images, and computers.
BMS is unavailable.

Further, in the RDBMS, it is currently difficult to obtain a sufficient speed for complicated processing, such as when a search that needs to perform a relatively complicated relational operation on a large amount of data.

An object of the present invention is to provide a database that can be easily and highly utilized such as adding a new data type.

Another object of the present invention is to provide a database that facilitates condition input for data search and history management of search results.

Another object of the present invention is to provide a database that enables the combination of an object-oriented database with an application that is not based on object orientation.

Another object of the present invention is to provide a database that facilitates design / change.

Another object of the present invention is to provide a database which ensures and facilitates input of data having a dependency relationship.

[0014]

In order to solve the above problems, the present invention provides a database using an object-oriented database management system, wherein the object-oriented database management system defines a class corresponding to a basic data type. Define and define a data search method and data display method for the data type, and define a class that encloses an arbitrary number of objects and configure one record, and interpret the search expression for the class. The function to describe the method to be executed and the method to interpret / execute the display layout, the data type defined by the user, the corresponding class, and the data search method and the data display method of the class are installed and pre-installed. Data structure of the record on the screen together with the data type Characterized in that a graphical user interface features to design a display layout as well as selected.

The present invention also provides a graphical user interface.
In the database having an interface function, the graphical user interface function accumulates a search expression automatic generation function input on a data search condition input screen and a search result history according to the input search expression. And a function of displaying, and a function of automatically generating a search expression obtained by performing a logical operation among a plurality of search results.

The present invention also provides an adapter provided between the application and the object-oriented database management system when the application not based on object-oriented is connected to a database having an object-oriented language, and the adapter is an application. A feature is that a conversion table is provided between the language used and the language used in the object-oriented database management system.

The present invention also provides a graphical user interface.
In the database having an interface function, the graphical user interface creates one class of the database by designing a screen for inputting / outputting data required for the database, and stores each item on the screen in the class. As a member, the class hierarchy is expressed by embedding the screen in another screen, and common items of a plurality of screens are extracted to generate an upper class.

Further, in the present invention, in the database for inputting / registering data having a dependency relationship through a user interface, the user interface uses a screen for displaying the data dependency relationship as a hierarchical structure as a data input screen, and the screen of the screen is displayed. It is characterized in that when each node is selected as the data of the dependency as a button, the display state of the data is switched and the transfer destination of the data is displayed.

[0019]

[Action]

(First invention) A database is constructed using an object-oriented database management system, a data search method and a data display method are described for object data types and class definitions, and data search and display by these methods are possible. To do. Also, the data GUI
Enables database construction by.

(Second invention) As a graphical user interface function, a new search expression is automatically created by logically operating between a search expression automatic generation function, a search result history storage / display function, and a search result. A function to generate it is provided to manage the history of search results so that it can be utilized for subsequent searches.

(Third invention) The object oriented database can be used without changing the application by converting an event or the like from an application not based on the object oriented into a language used in the object oriented database by an adapter. To do.

(Fourth invention) A database can be designed and changed from a screen design by a graphical user interface.

(Fifth Invention) A data input screen is used to display a data dependency relationship in a hierarchical structure so that data can be input and registered while confirming the data dependency relationship.

[0024]

【Example】

(First Embodiment) FIG. 1 is a system configuration diagram showing an embodiment of the present invention. In this embodiment, an object-oriented database management system (OODBMS) is used as a database management system that manages a database and provides services to users and application programs. Also, it enables the construction of a database using a GUI (graphical user interface).

An object-oriented database creates what is called an object by encapsulating data and member functions (methods) that access it, and defines classes of objects by grouping together types that have the same properties. Classes form a generalization hierarchy, and methods defined in a higher class can be inherited by lower classes.

In the creation of these objects and the class definition, in this embodiment, the object-oriented database management system 1 creates an object for the database 2 and defines the class, displays a screen on the display 3 by the GUI, and responds to the application 4. , The following functions are provided.

(1) A class library function for providing a class group and a function group for enabling definition and implementation of a basic data type is provided.

(2) In the class corresponding to each data type,
It enables the incorporation of basic data display methods and data search methods.

(3) A class generation function is provided so that an arbitrary number of objects of each data type (class) are combined to form one record.

(4) The class corresponding to the record is provided with a function of incorporating a basic method for displaying each internal object data as a search result on the screen.

(5) Select an arbitrary data type on the screen,
A corresponding item name is defined, a record type name is defined for a plurality of combinations thereof, and a graphical function is provided that enables designing a screen layout for displaying search results of that type.

(6) A mechanism that allows a user to define and implement the class library implemented on OODBMS into a construction tool and to operate in the same manner as a basic data type is provided.

2A and 2B show examples of built-in data types. FIG. 2A shows data input parts corresponding to various data types, and FIG. 2B shows data display parts associated with each data type. Indicates. The search methods for these data types are
For single-line text and multiple-line text, describe the matching using regular expressions, and for list text, describe the complete match of items.

By providing the various functions as described above, according to the present embodiment, the user can construct the database using the OODBMS with the same simple operability as in the case of the RDBMS.

Further, the user takes advantage of the characteristics of OODBMS and implements a new data type and means for acquiring, storing, retrieving, displaying, reusing data, etc. depending on the new data type, so that the database has a desired function. Can be added to realize an advanced usage method.

Further, for each item constituting one record of the database, a search is independently performed to enable narrowing down, so that it is not necessary to generate a table by a combination like a relational database, and memory efficiency is improved. It is advantageous in terms of utilization and execution speed.

(Second Embodiment) This embodiment relates to condition input for data search and history management of search results.

In the database, conventionally, there are two types of condition input means for data retrieval, a collation language format and a form format. Further, the stored data is operated in units of records whose types are defined and which are some fields.

For this data, the condition input in the collation language format uses a database inquiry language having a specific grammar to give the field name and the condition to be satisfied in the sentence format in order to obtain the corresponding record. .

The condition input in the form format is a so-called fill-in-the-blank expression, which is represented by a table having an array of fields in the horizontal direction and a record in the vertical direction, and the condition to be satisfied by the value in the target field column of the table. By specifying it as a concrete value, the corresponding record is obtained, and thereby the table is completely filled.

In each of these conventional methods, the function is completed by a single operation of designating the condition and returning the result, and it is impossible to manage the history of search results and utilize it for subsequent searches. Alternatively, if the number of search operations is stored as a management means, it cannot be used for subsequent searches.

Therefore, in this embodiment, the user can easily utilize the history of search results by visual search history management using the GUI.

FIG. 3 shows a search operation screen designed for a database. This screen is displayed on the display 3 of FIG. 1, and the GUI function of the OODBMS 1 is used for search operation and management.

In FIG. 3, the display content of each area is T1.
Is a database name, L1 to L7 are field names, L8 is a search result identification number, F1 and F3 to F6 are search condition input and result display, F2 and F7 are search result display, and F8 is a search result identification name input. , F9 is to display / edit the search condition expression,
F10 is a display of the number of the same records as the search result, B1 is a search button, B2 is a display / edit area clear button, B3 is a next display button of the same record, B4 is a previous display button of the same record, and B5 is a search history. A product operation button, B6 is a search result sum operation button, B7 is an equivalent record list display / search history list display switch button, and B8 is a search result delete button.

In this configuration, when the button B1 on the screen is designated, the search is executed and the automatically generated search formula is displayed in the area F9. Further, the number of equal records of the search result is displayed in the area F10. Area F8 if required
Make it possible to enter the meaning or name of the formula.

When button B7 is specified after the search is executed,
By displaying a list of corresponding records and selecting an arbitrary record from this display, the field value of the record can be known in each field value display area at the top of the screen.

Further, with respect to the search result, the user can add an arbitrary character string as an annotation, selectively delete the search result, and change the type of calculation and the priority order by editing the search expression. .

Further, by specifying the buttons B3 and B4, it is possible to sequentially display the contents of the corresponding records.
FIG. 4 shows an example of a list display screen of the equal records.

FIG. 5 shows an example of a search history list screen. In the figure, F11 is a search name list area of the search history, and F12
Is a search expression list area of the search history.

As described above, when the search history list screen is switched after the search is performed several times by changing the search condition according to FIG. 3 or 4, the area F11 is moved upward from the bottom end of the screen. And the search history accumulated in F12 is displayed.

In this display, when an arbitrary search result is selected and the operation of the product or the sum of the search results is designated by the buttons B5 and B6, the search conditions in which the latest search expressions are sequentially assembled are displayed in the areas F1 to F6. The search is executed by individually instructing the search with the button B1 for this search condition.

As a result, the change of the search condition by the logical operation between the search histories and the search according to the condition are executed, and a new history based on the execution is generated. Further, the unnecessary search result is deleted from the history with the button B8.

Therefore, according to the present embodiment, it is possible to manage the visual search history using the GUI, and the history of the search results can be easily utilized by the user for subsequent searches.

The present embodiment can also be used for a relational database.

(Third Embodiment) This embodiment is based on OODBM.
This is related to the exchange of information between S1 and the application 4.

Application 4 is not premised on object orientation, for example, M of window system
When trying to build a system that provides data from a database to the onif, conventionally, the application 4 cannot use the object-oriented database, but uses the relational database.

However, in the use of the relational database, the function of handling the data hierarchy is insufficient, the version management function is insufficient, the function of handling the graphic / image data is insufficient, and the transaction management function suitable for the design work is not available. Problems such as remain.

Although an object-oriented database can be used as a method for solving these problems, it cannot be used because the application 4 does not consider the object-oriented database.

The present embodiment is an object-oriented database which enables connection with an application which is not premised on object orientation.

This embodiment is an object-oriented database management system (OODBM) described in C ++ language.
S) An adapter is provided between 1 and the application 4.

This adapter is provided with a format conversion table for a language (for example UNIX) that is compatible with the application 4 and a language (C ++) that is compatible with OODBMS.

For example, the application 4 can use the C language function, but cannot use the C ++ language function used by the object-oriented database management system 1. At this time, the adapter becomes a function equivalent to the function “my-new” from the application 4, for example.
It is converted into a function "new" of ++ language and passed to OODBMS1.

Therefore, according to the present embodiment, it is possible to access the OODBMS 1 by picking up an event from the keyboard or mouse from the application 4 side.

(Fourth Embodiment) This embodiment is based on OODBM.
It relates to a GUI (Graphical User Interface) provided in S1.

Usually, the database design and the user interface design are carried out independently of each other, and more generally, the database design is carried out first, and the data necessary for this is input and displayed. The user interface is designed.

Such individual design has the following problems.

(1) When the design of the database is changed,
Therefore, the user interface needs to be changed accordingly. At this time, in order to identify all the data related to the change, and to add or modify the data, the larger the program, the more labor is required, and the more overlooked the data becomes.

(2) When the number of data items is large, the work of linking each data on the database and each item on the user interface is to repeat the same procedure for each data item in terms of content. It will be a very difficult task.

Therefore, in this embodiment, it is possible to easily change the user interface according to the design change of the database.

In this embodiment, contrary to the conventional method, the object-oriented database is analyzed, and the database design is analyzed from the graphical user interface design to automatically generate the source code.

The object-oriented database has, for example, "postal code", "prefecture name", "city name", and "address" as items (data members) of the class "address". Also, it has “name”, “age”, “phone number”, “address”, and “occupation” as items of the class “personal”.

In these two class relationships, the "address" is
It is one class and one of the classes of "individual"
There is an inheritance relationship that is one item.

Considering a class as one screen (hereinafter, this screen is called a plate), and a data member in a class is considered as an input / output item on the plate (hereinafter, this item is called an item). By designing the screen for inputting / outputting the necessary data to / from the database, one class can be created at the same time.

In the object-oriented database, the class can be treated as one data on the database. Therefore, in this embodiment, the object-oriented database is designed by designing the screen with the graphical user interface. In addition, the class hierarchy is expressed by embedding the already designed plate in another plate.

Further, the graphical user interface automatically generates a variable for saving the content of each item and a method for inputting / outputting the variable. Also, if necessary, describe the item name, data type, linked item names and classes, and their relational expressions as attributes of each item,
Perform more detailed operations.

Further, the graphical user interface reduces the code amount by extracting the common part from some already registered plates, making it independent as a new plate, and treating it as one class.

Therefore, according to this embodiment, the database can be designed by the screen design of the graphical user interface, and the efficiency can be improved. It also makes it easier to change the database. In addition, the existing database can be reused easily and redundant code can be reduced.

(Fifth Embodiment) This embodiment relates to registration of data (including hierarchy and attribute values) in a database by a user interface.

Generally, registration of data in the database is performed by inputting from a keyboard. At this time, if the data to be registered has a dependency relationship (parent-child relationship, hierarchical relationship, etc.), it is necessary to register data belonging to the upper or lower order of the data. The input of the data item indicating such a dependency relationship is performed by the input from the keyboard or the selection from the registered data list menu.

For example, as shown in FIG. 6A, the data items are "division", "population", and "subdivision",
When inputting the data as shown in (b), the input is made from the keyboard or the list menu.

Here, the data input screen is different from the display screen of the hierarchical structure of the data created thereby. For example, FIG. 7A shows a data input screen using a keyboard, FIG. 7B shows a data input screen using a list menu, and FIG. 7C shows a hierarchical display screen.

From the above, in the data input by the keyboard, since the data is directly written in the lower section of the input screen, a. Possible typographical errors, b. Inability to reuse already entered data, c.
It is difficult to understand the hierarchical structure of data, d. There is a problem such as not being able to check the consistency between the data (in the case shown, the population is the sum of the subdivisions).

Further, in the data input from the list menu, candidates are searched from the already registered data, so the problems of a, b and d in the case of the keyboard are solved, but c
The problem of remains. Further, since three screens are used, there is a problem that the display space becomes small.

Therefore, in the present embodiment, the input of data having a dependency relationship is ensured and facilitated.

In this embodiment, the hierarchical structure display screen is also used as the selection screen for data input. Specifically, (1) By treating each node (Japan, Tokyo, etc.) on the hierarchical structure display screen illustrated in FIG. 7C as a button, the same function as the menu selection screen is provided.

(2) The input area of the input screen is also made into a button. In this way, in cooperation with the hierarchical structure display screen, it becomes clear to which part of the input screen the data is transferred when a node on the hierarchical structure display screen is selected.

(3) In (2) above, in order to clearly recognize that each node of the hierarchical structure display screen is a selection target for data input, the colors of the entire screen are switched. Switch the display state.

Data input according to this embodiment is performed by clicking the text input area in the lower section of the input screen with a mouse or the like,
This changes the color of the hierarchical display screen. Then, the node of the hierarchical structure display screen is clicked with a mouse or the like, and thereby data is transferred to the text area of the input screen. Data is input by repeating the above input operation.

Therefore, according to this embodiment, the data input can be performed by clicking the mouse while looking at the hierarchical structure display screen, and the following effects can be obtained.

(1) The number of input operations from the keyboard is reduced.

(2) Inputting invalid data due to a typo is eliminated.

(3) Since dependency data can be input while visually confirming the hierarchical structure, theoretical input errors (misidentification of hierarchical position, etc.) are reduced.

(4) Since the data is created while displaying the hierarchical structure, it is necessary to search the database when inputting the data by simultaneously adding the data necessary for checking the consistency caused by the dependency. It is eliminated and the operation speed is improved. That is, it is necessary to search what the input data is by the input from the keyboard, but in the present embodiment, it is not necessary to search the database because the data is directly specified.

(5) Compared with the menu type input method,
Requires less display space.

[0095]

As described above, according to the present invention, an object-oriented database management system is used to construct a database, a data retrieval method and a data display method are described for the data type and class definition of an object, and these methods are described. In addition to the new data type addition function of the object-oriented database management system in order to enable data retrieval and display by using the data GUI and the database construction using the data GUI, the same convenience as a relational database management system It has the advantage of being able to build a database that can be used at a high level, and has excellent memory efficiency and execution speed.

Further, according to the present invention, in a database having a graphical user interface function, as a graphical user interface function, an automatic generation function of a search expression and a storage of history of search results
Since the display function and the function of automatically generating a new search expression by performing a logical operation between the search results are provided, the user can utilize the history of the search results for later searches.

Further, according to the present invention, since an adapter for converting an event or the like from an application which is not based on object orientation into a language used in the object oriented database is provided by the adapter, the application can use the object oriented database. Therefore, it is possible to build a system using an object-oriented database even if the application is not premised on object-oriented.

Further, according to the present invention, since the database design and the change can be performed from the screen design by the graphical user interface, the efficiency of the database design and the easy design change can be performed.

Further, according to the present invention, since the screen for displaying the data dependency as a hierarchical structure is the data input screen, the data can be input and registered while confirming the data dependency, and the data input operation is simple. Make sure to enter and register.

[Brief description of drawings]

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

FIG. 2 is an example of a data type in the embodiment.

FIG. 3 is an example of a search operation screen according to the embodiment.

FIG. 4 is an example of the equal record list screen in the embodiment.

FIG. 5 is an example of a search history list screen in the embodiment.

FIG. 6 shows an example of data input items in the embodiment.

FIG. 7 is an example of a data input / display screen in the embodiment.

[Explanation of symbols]

 1 ... Object-oriented database management system 2 ... Database 3 ... Display 4 ... Application

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification code Internal reference number FI technical display location 9365-5H 15/62 322 K

Claims (5)

[Claims] 1. In a database using an object-oriented database management system, the object-oriented database management system defines a class corresponding to a basic data type and defines a data search method and a data display method for the data type. Function to describe, function to define a class that encloses an arbitrary number of objects and configure one record, and to describe a method that interprets / executes a search expression for that class and a method that interprets / executes a display layout And a data type defined by the user, a class corresponding to the data type, a data search method and a data display method of the class are incorporated, and the data structure of the record is selected on the screen in combination with the data type incorporated in advance. Graphical designing display layout with A database having a user interface function. 2. In a database having a graphical user interface function, the graphical user interface function includes an automatic generation function of a search expression input on a data search condition input screen, and the input search expression. A database having a function of accumulating and displaying a history of search results according to the above, and a function of automatically generating a search expression that is a logical operation between a plurality of search results. 3. When connecting an application not based on object-oriented to a database having an object-oriented language, an adapter is provided between the application and the object-oriented database management system, and the adapter is a language used by the application. A database that is provided with a conversion table for a language used in an object-oriented database management system. 4. In a database having a graphical user interface function, the graphical user interface creates one class of the database by designing a screen for inputting / outputting data required for the database, and the screen is created. A database, wherein each of the above items is a data member in the class, a class hierarchy is expressed by embedding the screen in another screen, and common items of a plurality of screens are extracted to generate a higher class. 5. In a database for inputting / registering data having a dependency relationship through a user interface, the user interface uses a screen for displaying the data dependency relationship as a hierarchical structure as a data input screen, and buttons for each node of the screen. When the data is selected as the dependency data, the display state of the data is switched and the transfer destination of the data is displayed.