JP3824468B2 - Data management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a data management system that performs data operations such as storage and retrieval of data like a database, and more particularly, to efficient instruction for data operations.
[0002]
[Prior art]
Conventionally, a relational database (RDB) has been provided with tools for performing data operations such as search and update for data stored in the database, and atypical search is possible by giving a search instruction using the database language SQL. Met. FIG. 11 is a schematic block diagram of a conventional RDB system. The system shown in FIG. 11 includes a database 2 for storing data to be searched and updated, a database search / update processing unit 4 for searching and updating the database 2, a search / update condition instruction and search, and an update result display. A search / update condition file 8 that stores the search / update condition file 8 and a search / update condition management unit 10 that manages the search / update condition file 8. Composed.
[0003]
The user interface unit 6 includes output means such as a display device and input means such as a mouse. The user interface unit 6 shows a schematic diagram of screen display of the display device. As shown in the screen display 12, when the search / update condition 14 is specified by the operator, the database search / update processing unit 4 performs a search / update process on the database 2, and the result is the search / update result 16. Is displayed.
[0004]
The search / update condition management unit 10 also displays a list 20 of search / update conditions stored in the search / update condition file 8 as shown in the screen display 18. The operator can select and specify the search / update condition 14 from the list 20. As described above, the search / update conditions once entered are stored in the search / update condition file 8 and reused, thereby improving the efficiency of data operation instructions for the database. As such a conventional technique, Japanese Patent Laid-Open No. 7-134717 discloses that used search conditions are stored in a history information file, and the search conditions are displayed in a list together with search history information such as access time, thereby improving operator efficiency. An information search system that supports general search processing is disclosed.
[0005]
In addition, there is a technique in which a part of the search condition is specified as a parameter, whereby the search condition is partially changed and reused. In this technique, for example, by specifying the value of the search condition value “10 years old” in the search condition “children under 10 years of age”, the portion can be changed to another value.
[0006]
FIGS. 12 to 16 are explanatory diagrams for explaining the specification of search conditions in the prior art, taking as an example the task of searching for candidates in personnel changes, and FIGS. 12 and 13 are staff members of the personnel management database, respectively. It is a schematic diagram of a file and a qualification file. 14 to 16 are explanatory diagrams showing search conditions and search results in each step of an example of the data operation work. The staff file shown in FIG. 12 stores information such as the current affiliation and job title as well as basic information such as the name and date of birth of the staff. The qualification file shown in FIG. 13 stores qualification information held.
[0007]
Here, it is assumed that this database is a relational type, and that retrieval is possible by giving a retrieval condition by an SQL sentence. When an operator searches for a staff member who has the qualification of “English proficiency” and displays the staff member, staff number, department, etc., the search condition is designated by the SQL statement 30 shown in FIG. . In response to this, the staff file and the qualification file are searched, and a search result 32 is obtained.
[0008]
Next, for example, in order to examine the influence on the department to which the operator is moved when the candidate is moved, the operator performs a work of listing staff members of the department. Here, since the “General Affairs Division” staff is listed in the search result 32, the operator specifies the search conditions in the SQL sentence 34 shown in FIG. 15, and the information on the staff of the “General Affairs Section” is listed. A search result 36 is obtained.
[0009]
When the operator determines that the transfer person can be selected from the “General Affairs Division” based on the search result 36, the operator searches for an employee of the “General Affairs Division” who has “English proficiency” as the possession qualification. Detailed information is displayed, and it is determined whether or not it is appropriate as a transfer target. The search condition for this purpose is designated by the SQL statement 38 in FIG. 16, and the search result 40 is obtained.
[0010]
For example, in the initial stage of narrowing down, only some data items of the search target file are displayed so that the search result is easy to see, while in the final stage, many data items related to candidates are displayed. Is done. As described above, the data items described in the SQL sentence can be changed at each stage of the search. Also, the search target file specified below “FROM” in the SELECT statement and the search condition specified below “WHERE” can be changed according to each stage of the search.
[0011]
In the prior art, in this example, the value of the search condition specified below “WHERE”, for example, the part “General Affairs Division” in the SQL statement 34 can be replaced with another value by enabling parameter specification. it can. On the other hand, for example, when the data items are different in each step, the operator inputs a new SQL sentence from the keyboard, adds or deletes a data item using an editor based on the SQL sentence 30, and deletes the SQL sentence. Make corrections.
[0012]
[Problems to be solved by the invention]
As described above, in the prior art, when the data operation condition is reused, basically, the operator must correct the description of the data operation condition sentence by typing using a keyboard and an editor. That is, there is a problem that even if reuse is performed, a considerable amount of manual work is still necessary for correction, and the efficiency of data manipulation work such as retrieval is low. In addition, it is sometimes difficult for a person who is unfamiliar with a search instruction such as an SQL sentence to perform a correction operation that allows the operator to describe a conditional sentence on which a desired data operation is performed.
[0013]
The present invention has been made in order to solve the above-described problems. Data management that allows data manipulation conditions to be reused, makes it easy for an operator to correct data manipulation conditions, and improves the efficiency of data manipulation instructions. The purpose is to provide a system.
[0014]
[Means for Solving the Problems]
The data management system according to the present invention includes a target file portion in which a target file for data operation is indicated A conditional part that is part of a data manipulation conditional statement that is written in database language And a data item part indicating a data item to be selected from among the data items included in the target file Conditional parts consisting of And a condition part that shows the search conditions for the target file At least three conditional parts consisting of In a data management system for performing data operations on data stored in a storage device based on data operation conditions including data, condition storage means for storing the data operation conditions, target file portions and data included in a plurality of data operation conditions Item part and condition part Each condition part Each to create a new data manipulation condition Condition parts A rule storage means for storing a condition generation rule that defines a combination rule for the data, and a rule file storing a target file part, a data item part, and a condition part included in at least two data operation conditions selected from the condition storage means Based on the condition generation rule selected from the means Condition parts And condition generation means for generating a new data operation condition by combining and editing each.
[0015]
Another data management system according to the present invention configures the previous data operation condition. Includes at least one of the target file part, data item part, and condition part There is a parts accumulating means for accumulating conditional parts, the rule storing means stores a condition generating rule for generating a new data operation condition using the existing conditional parts, and the condition generating means includes the parts The new data operation condition is generated using the condition part selected from the storage means.
[0016]
Another data management system according to the present invention includes a condition search unit that searches the condition storage unit and extracts the data operation condition including a designated template, and the rule storage unit includes the condition storage unit. Stores a template generation rule for extracting the data operation condition part selected from the template and generating the template The condition generation means uses the data operation condition selected from the condition accumulation means and the condition part selected from the parts accumulation means based on the template generation rule selected from the rule storage means. Generate the template To do.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments of the present invention will be described with reference to the drawings.
[0018]
[Embodiment 1]
FIG. 1 is a schematic block diagram of an RDB system according to the first embodiment of the present invention. The system shown in FIG. 1 includes a database 50 that stores data to be searched and updated, a database search / update processing unit 52 that searches and updates the database 50, and search / update conditions for the database search / update processing unit 52 (hereinafter referred to as the database search / update processing unit 52). , Data operation conditions), a user interface unit 54 for displaying the results of data operations such as search and update, a condition accumulation file 56 for storing the conditions for reusing data operation conditions, and data operation conditions. A rule storage file 58 for storing condition generation rules (to be described later) for editing and generating new data operation conditions, a condition storage file 56, a data operation condition management unit 60 for managing the rule storage file 58, and a condition generation rule A condition generation unit 62 that generates a data operation condition based on the data operation condition is included.
[0019]
The user interface unit 54 includes output means such as a display device and input means such as a mouse. The user interface unit 54 shows a schematic diagram of screen display of the display device. As shown in the screen display 70, when the data operation condition 72 is specified, the database search / update processing unit 52 performs a data operation such as search / update on the database 50, and the result is displayed as the data operation result 74. .
[0020]
Further, as shown in the screen display 80, the data operation condition management unit 60 displays a list 82 of data operation conditions stored in the condition accumulation file 56 and a list 84 of condition generation rules stored in the rule storage file 58. Let The operator can select and specify, for example, two data operation conditions from the data operation condition list 82, and these are displayed as the first data operation condition 86 and the second data operation condition 88 on the screen. Further, the operator can select and specify a condition generation rule to be applied to the data operation conditions 86 and 88 from the list 84, and this is displayed as the condition generation rule 90 on the screen.
[0021]
Next, the condition generation rule will be described. In this system, the condition generation unit 62 edits two existing data operation conditions 86 and 88 to generate a new data operation condition, and uses this as the data operation condition 72 to perform data operation on the database 50. An editing rule for the two data operation conditions at this time is a condition generation rule. FIG. 2 is a schematic diagram of the condition generation rules stored in the rule storage file 58. Here, it is assumed that the first data operation condition 86 is a SQL statement of a search operation having the following format.
[0022]
SELECT data item 1 FROM target file 1 WHERE condition 1
Further, it is assumed that the second data operation condition 88 is a SQL statement of a search operation having the following format.
[0023]
SELECT data item 2 FROM target file 2 WHERE condition 2
The data operation condition for performing a search newly generated by the condition generation rule,
SELECT data item N FROM target file N WHERE condition N
In FIG. 2, for example, the condition generation rule “logical product” is
Data item N = OR of “data item 1” and “data item 2”
Target file N = OR of “target file 1” and “target file 2”
Condition N = AND of "condition 1" and "condition 2"
This indicates that a new data operation condition is generated from the first data operation condition and the second data operation condition based on the rule. Although FIG. 2 shows only the case where the data operation condition is a search condition, a condition generation rule can be defined for other data operations such as update processing and stored in the rule storage file 58.
[0024]
Next, an example of data operation in this system will be specifically described. Here, in order to facilitate comparison, the same data operation as described in the prior art is performed, and after a search operation is performed using the SQL statement 30 and the SQL statement 34, a new SQL statement 38 is generated according to the condition generation rule. An example of generating
[0025]
In this system, an operator can input and create data operation conditions from a keyboard. The created data operation conditions can be registered and accumulated in the condition accumulation file 56. Data operation conditions generated by the condition generation rules can also be registered and stored in the condition storage file 56.
[0026]
The SQL statements 30 and 34 are input by the operator or created by rules, and are used for search processing and registered in the condition accumulation file 56.
[0027]
Next, the operator attempts to create a SQL sentence 38 that performs a process of displaying a list of detailed information on the staff members of the “General Affairs Division” who have the qualification of “English proficiency”. At this time, the operator switches the display device to the screen display 80. Then, it is examined whether the SQL statement 38 can be generated by combining the existing data operation condition displayed in the data operation condition list 82 and the condition generation rule displayed in the condition generation rule list 84. In this example, the conclusion is that the SQL statements 30 and 34 and the condition generation rule “logical product” may be combined.
[0028]
Therefore, the operator selects the SQL statements 30 and 34 displayed in the data operation condition list 82 as the first data operation condition and the second data operation condition. This selection operation can be configured to be realized by clicking a desired data operation condition displayed in the data operation condition list 82 with a mouse. For example, the data operation condition that is clicked first is set as the first data operation condition and displayed in the column of the data operation condition 86, and the data operation condition that is clicked next is set as the second data operation condition. It is displayed in the condition 88 column.
[0029]
Further, the operator selects the condition generation rule “logical product” displayed in the condition generation rule list 84 by operating the mouse or the like, and the condition generation rule name “logical product” is displayed in the column of the condition generation rule 90.
[0030]
When the selection of the data operation condition and the condition generation rule is thus completed, the operator instructs the system to generate a new data operation condition. The system generates a new data operation condition in the condition generation unit 62 and switches the display device from the screen display 80 to the screen display 70. Then, a new data operation condition generated based on the set first data operation condition, second data operation condition and condition generation rule is displayed in the column of the data operation condition 72, and a database search is performed according to the data operation condition. The data operation result 74 executed by the update processing unit 52 is displayed. In this example, the SQL statement 38 is displayed in the data operation condition 72, and the search result 40 is displayed in the data operation result 74.
[0031]
In the above example, both the first data operation condition and the second data operation condition are selected from the data operation condition list 82. However, either one of the first data operation condition and the second data operation condition is directly selected by the operator using the keyboard. You may enter in the column of conditions 86 and 88. In addition, the condition generation rule is exemplified as one that generates one new data operation condition from two data operation conditions, but it is also possible to define a rule that generates one data operation condition from three or more data operation conditions. Is possible.
[0032]
As described above, in this system, data operation conditions used in the past are accumulated, and past data operation conditions similar to newly required data operation conditions are edited and reused. Data operation conditions may represent a large number of data items and complicated conditions, and are often relatively long. However, according to the present system, the operation of directly describing the data operation conditions using an input means such as a keyboard is possible. This reduces the efficiency of data operations such as database search and update. In addition, editing and reusing existing data manipulation conditions makes it easier for typographical errors and grammatical errors to occur, making it easier to manipulate data, especially when someone unfamiliar with creating data manipulation conditions. It becomes.
[0033]
[Embodiment 2]
In the following description of the second embodiment of the present invention, the same components as those in the first embodiment are denoted by the same reference numerals to simplify the description.
[0034]
FIG. 3 is a schematic block diagram of an RDB system according to the second embodiment of the present invention. The system shown in FIG. 3 includes a condition part storage file 100 for storing the data operation condition portion in addition to the condition storage file 56 for storing the data operation condition itself in order to reuse the data operation condition. The rule storage file 102 stores a condition generation rule for editing a data operation condition stored in the condition accumulation file 56 and a condition part stored in the condition part accumulation file 100 to generate a new data operation condition. The condition part accumulation file 100 and the rule storage file 102 are managed by the data operation condition management unit 104 together with the condition accumulation file 56. The data generation condition is generated by the condition generation unit 105 based on the condition generation rule.
[0035]
The user interface unit 106 of the present embodiment is different from the user interface unit 54 of the above-described embodiment in that the screen display 110 obtained by adding the conditional parts list 108 to the display content of the screen display 80 is presented to the operator. The conditional parts list 108 is a list of conditional parts stored in the conditional parts storage file 100.
[0036]
The operator can select and specify two data operation conditions or condition parts from one or each of the data operation condition list 82 and the condition parts list 108, and the two data operation conditions or condition parts. Are displayed as a first data operation condition 86 and a second data operation condition 88 on the screen.
[0037]
FIG. 4 is a schematic diagram of an example of the conditional parts storage file 100. For example, the condition part “all data items” includes all the data items of the staff file and the qualification file, and has the form “SELECT qualification file and all data item list of the qualification file”. This conditional part does not include the specification of the target file of the SQL statement and the specification of the condition, and is only a part of the SQL statement. The condition part “age restriction” is a search condition that specifies a date of birth range for the staff file. This conditional part has a format of “FROM target file WHERE condition” and has only a description of the latter half of the SQL statement.
[0038]
The rule storage file 102 stores not only a condition generation rule for generating a new data operation condition by editing a data operation condition but also a condition generation rule for generating a new data operation condition using a conditional part. For example, the condition generation rules “data item logical sum”, “data item logical product”, and “data item replacement” stored in the rule storage file 58 of the above embodiment shown in FIG. And a rule applicable to a conditional part including “data item 2” and a complete data manipulation condition. Also, for example, the condition generation rules “conditional logical product” and “conditional logical sum” shown in FIG. 2 are rules applicable to two complete data manipulation conditions, and at the same time, “target file 2” and “condition 2”. It is also a rule that can be applied to conditional parts containing "and complete data manipulation conditions. Therefore, for example, the rule storage file 58 can be used as it is as the rule storage file 102 of the present embodiment.
[0039]
Next, an example of data operation in this system will be specifically described. Here, first, description will be made by taking as an example a case where it is desired to display all data items of the staff file and the qualification file by adding data items as a result of searching by the SQL sentence 38 exemplified in the prior art. FIG. 5 is an explanatory diagram showing data operation conditions (SQL sentence 120) necessary for displaying all the data items, and search results 122 obtained thereby. In this case, it is possible to edit the data operation condition based on the existing SQL sentence 38 and generate a new SQL sentence 120 required here. Specifically, a new SQL statement 120 can be obtained by adding the data item of the conditional part “all data items” shown in FIG. 4 to the data item of the SQL statement 38.
[0040]
An operation for obtaining the SQL sentence 120 will be described. The operator selects the SQL sentence 38 displayed in the data operation condition list 82 and the condition part “all data items” displayed in the condition parts list 108. The selected SQL sentence 38 and condition part “all data items” are displayed in data operation conditions 86 and 88, respectively. Further, the operator selects and specifies the condition generation rule “data item logical sum” to be applied to the SQL statement 38 and the condition part “all data items” from the condition generation rule list 84, and this is displayed on the screen as a condition. It is displayed as a generation rule 90.
[0041]
When the selection of the data operation conditions 86 and 88 and the condition generation rule 90 is completed as described above, the operator instructs the system to generate a new data operation condition. The system activates the condition generation unit 105 to generate a new data operation condition based on the set SQL sentence 38, the condition part, and the condition generation rule, and switches the display device from the screen display 110 to the screen display 70. Then, the generated new data operation condition is displayed in the data operation condition 72 column.
[0042]
By using the condition generation rule “data item logical sum”, the target file and the condition are extracted from the SQL statement 38 specified as the first data operation condition, while the data item and the condition of the SQL statement 38 are included in the data item. The logical sum with the part "all data items" is specified. In this way, the SQL sentence 120 is generated and displayed in the column of the data operation condition 72. The data operation result 74 displays the search result 122 shown in FIG.
[0043]
As another example, after performing a search using the SQL sentence 30 exemplified in the prior art, the “year of experience is prior to S55.4.1” condition is further refined with respect to “year of experience”. Explain the case. FIG. 6 is an explanatory diagram showing data operation conditions (SQL sentence 130) necessary for the narrowing search and search results 132 obtained thereby. In this case, the data manipulation condition is edited based on the existing SQL statement 30, the condition part of the condition part “experience years limit” and the condition generation rule “conditional OR” shown in FIG. A simple SQL statement 130 can be generated. In other words, the condition generation unit 105 rewrites the target file portion of the SQL statement 30 with the logical sum of the target file of the SQL statement 30 and the target file specified in the conditional part, with the data items of the SQL statement 30 unchanged. The SQL statement 130 is generated by rewriting the condition portion of the SQL statement 30 with the logical product of the condition portion of the SQL statement 30 and the condition part of the condition part “experience years limit”.
[0044]
The operation for obtaining the SQL statement 130 is the same as that for obtaining the SQL statement 120. That is, the operator selects the SQL sentence 30 displayed in the data operation condition list 82 and the condition part “experience years limit” displayed in the condition parts list 108. The selected SQL sentence 30 and the condition part “experience years limit” are displayed in the columns of the data operation conditions 86 and 88, respectively. Further, the operator selects and designates the condition generation rule “conditional AND” to be applied from the condition generation rule list 84 and displays it in the condition generation rule 90 field on the screen.
[0045]
After the selection of the data operation conditions 86 and 88 and the condition generation rule 90 is completed, the condition generation unit 105 is activated based on an instruction from the operator, and based on the set SQL sentence 30, the condition part, and the condition generation rule. A new data operation condition is generated, and the system displays this in the data operation condition 72 column.
[0046]
As described above, in this system, the data operation condition components such as data items and conditions among the data operation conditions used in the past are accumulated in the condition part accumulation file 100, and the data operation conditions are generated using the accumulated data operation condition elements. The similarity between past data manipulation conditions and newly required data manipulation conditions is likely to be partial rather than overall, and the reuse of data manipulation conditions is similar Often in partial units. Therefore, by accumulating in the form of components of data operation conditions, editing work for generating new data operation conditions is facilitated. In particular, it is significant to register the frequently used components in the conditional parts storage file 100 in advance.
[0047]
[Embodiment 3]
In the following description of the third embodiment of the present invention, the same components as those in the above-described embodiments are denoted by the same reference numerals to simplify the description.
[0048]
FIG. 7 is a schematic block diagram of an RDB system according to the third embodiment of the present invention. In the system of FIG. 7, the data operation condition management unit 150 includes a condition search unit 152. When a data operation condition part (hereinafter referred to as a template) is designated, the condition search unit 152 searches the condition accumulation file 56 and extracts a data operation condition including the template. The template can be generated by editing existing data operation conditions. The template generation rule used for generating the template is stored in the rule storage file 154, for example. The condition generation unit 156 performs a data operation condition generation process based on the same condition generation rule as in the above-described embodiment, and also performs a template generation process based on the template generation rule. Incidentally, the template generation process and the data operation condition search process using the template are started by an instruction from the operator. For this purpose, for example, a configuration is adopted in which buttons that can be operated with a mouse or the like are displayed on the screen.
[0049]
Next, an example of generation and use of a template in this system will be described. 8-10 is explanatory drawing used for this description. FIG. 8 is a schematic diagram of the screen display 110. In FIG. 2 shown in the first embodiment, the condition generation rule “data item reduction” can be used as a template generation rule. The operator selects “data item reduction” displayed in the condition generation rule list 84 in order to generate a template. As a result, the condition generation rule 90 displays the rule name “data item reduction”. The operator selects, for example, the SQL statement 30 for qualification search from the data operation condition list 82 and selects the condition part “all data items” from the condition generation rule list 84. As a result, the SQL statement 30 is displayed in the data operation condition 86, and the condition part “all data items” is displayed in the data operation condition 88.
[0050]
For example, when the template generation process is activated by operating a button (not shown) displayed on the screen, the condition generation unit 156 generates a new data operation condition according to the specified condition generation rule. The generated data operation condition is displayed on the screen as a template. In this example, the template 170 shown in FIG. 9 is displayed on the screen. Since all the data items of the SQL statement 30 are included in the data items described in the condition part “all data items”, the SQL items in which all the data items of the SQL statement 30 are deleted by the condition generation rule “data item deletion” A sentence is generated as a template.
[0051]
When the operator decides to use this template 170 and instructs the retrieval of the data operation condition, the process in the condition retrieval unit 152 is activated. The condition search unit 152 searches and extracts data operation conditions stored in the condition storage file 56 that include a description that matches the template 170, and displays the list on the screen. For example, as shown in FIG. 10, an SQL sentence 172 for qualification / department search and an SQL sentence 174 for qualification search with job history restriction are acquired from the condition accumulation file 56 and displayed.
[0052]
The operator can select a desired one of the data operation conditions acquired and displayed in a list by the condition search process and instruct the database search / update processing unit 52 to perform the data operation.
[0053]
A large number of data operation conditions can be stored in the condition storage file 56. Therefore, the task of finding a desired data operation condition from all the list displays may be complicated and time consuming. According to the present system, the data operation conditions having desired characteristics are narrowed down by the matching process with the template, so that it becomes easy to find the necessary data operation conditions. Further, since the template is generated based on the template generation rule using the existing data operation conditions and condition parts without directly inputting with a keyboard or the like, the number of steps for creating the template is also reduced.
[0054]
【The invention's effect】
According to the data management system of the present invention, since a new data operation condition is generated from an existing data operation condition based on the condition generation rule, the work of directly describing the data operation condition by an input means such as a keyboard is reduced. This has the effect of improving the efficiency of data operations such as database search and update. In addition, editing and reusing existing data manipulation conditions makes it easier for typographical errors and grammatical errors to occur, making it easier to manipulate data, especially when someone unfamiliar with creating data manipulation conditions. The effect becomes.
[0055]
Further, according to the data management system of the present invention, there is an effect that the editing work is facilitated by accumulating the condition parts constituting the data operation conditions and using them for editing the data operation conditions.
[0056]
Further, according to the data management system of the present invention, a template is generated based on a template generation rule using existing data operation conditions and the like, and only a matching item is presented to the operator. Even when a large number of data is accumulated, it is possible to easily find a desired one. Further, since it is not necessary for an operator to manually input directly using a keyboard or the like in order to generate a template, there is an effect that creation of the template itself is easy.
[Brief description of the drawings]
FIG. 1 is a schematic block configuration diagram of an RDB system according to a first embodiment of the present invention.
FIG. 2 is a schematic diagram of condition generation rules stored in a rule storage file.
FIG. 3 is a schematic block configuration diagram of an RDB system according to a second embodiment of the present invention.
FIG. 4 is a schematic diagram of an example of a conditional parts storage file.
FIG. 5 is an explanatory diagram showing data operation conditions necessary for displaying all data items of a staff file and a qualification file, and search results obtained thereby;
FIG. 6 is an explanatory diagram showing data operation conditions necessary for a narrowing search and search results obtained thereby.
FIG. 7 is a schematic block diagram of an RDB system according to a third embodiment of the present invention.
FIG. 8 is a schematic diagram showing an example of a screen display for performing designation for generating a template.
FIG. 9 is an explanatory diagram illustrating an example of a generated template.
FIG. 10 is an explanatory diagram illustrating an example of data operation conditions extracted by matching with a template.
FIG. 11 is a schematic block diagram of a conventional RDB system.
FIG. 12 is a schematic diagram of a staff file in a personnel management database.
FIG. 13 is a schematic diagram of a qualification file of a personnel management database.
FIG. 14 is an explanatory diagram showing search conditions and search results in a qualification search step in an example of data manipulation work.
FIG. 15 is an explanatory diagram showing a search condition and a search result in a department search step in an example of a data operation work.
FIG. 16 is an explanatory diagram showing search conditions and search results in a qualification / department search step in an example of data manipulation work;
[Explanation of symbols]
50 database, 52 database search / update processing unit, 54, 106 user interface unit, 56 condition accumulation file, 58, 102, 154 rule storage file, 60, 104, 150 data operation condition management unit, 62, 105, 156 condition generation Part, 82 data operation condition list, 84 condition generation rule list, 86, 88 data operation condition, 90 condition generation rule, 100 condition part storage file, 108 condition part list, 152 condition search part.

Claims (3)

A data item to be selected is selected from a conditional part that is a part of a data operation conditional statement that is composed of a target file portion in which a target file for data operation is indicated and is described in a database language, and a data item included in the target file. Data for data stored in a storage device based on a data operation condition including at least three condition parts including a condition part composed of a data item part and a condition part composed of a condition part indicating a search condition for the target file In a data management system that performs operations,
Condition accumulation means for accumulating the data operation conditions;
The combination rules for each condition part for creating new data operation conditions by combining the target file part, data item part, and condition part included in multiple data operation conditions for each condition part and editing them were established. Rule storage means for storing condition generation rules;
A target file part, a data item part, and a condition part included in at least two data operation conditions selected from the condition storage unit are combined for each condition part based on the condition generation rule selected from the rule storage unit. Condition generation means for editing and generating new data operation conditions;
A data management system comprising: A part accumulating unit for accumulating a conditional part including at least one of a target file part, a data item part, and a condition part constituting the data operation condition;
The rule storage means stores a condition generation rule for generating a new data operation condition using the existing condition part,
The condition generation means generates the new data operation condition using the condition part selected from the parts storage means;
The data management system according to claim 1. Searching the condition storage means, and having a condition search means for extracting the data operation condition including the specified template,
The rule storage means stores a template generation rule for generating the template by extracting a portion of the data operation condition selected from the condition storage means,
The condition generation means uses the data operation condition selected from the condition storage means and the condition part selected from the parts storage means based on the template generation rule selected from the rule storage means. Generating,
The data management system according to claim 1 or 2, characterized by the above.

Images