JP4481856B2 - Database creation system - Google Patents

Description

  The present invention relates to a database creation system, and more particularly to a database creation system suitable for creating a database of data having a parent-child relationship.

  Conventionally, as a system for creating a database, for example, a system using a spreadsheet software sheet as described in Japanese Patent Application Laid-Open No. 2003-15920 is known. In this way, using a spreadsheet software sheet that is commonly used makes it easier for general operators to input data for the database compared to using dedicated utility software. Can do.

JP 2003-15920 A

  However, as described in Japanese Patent Laid-Open No. 2003-15920, even when a spreadsheet software sheet is used, there is a problem that data input is not easy for data having a parent-child relationship between data. In addition to parent-child relationships, there is a mutual relationship between data (categorization of whether data cannot be combined or a combination is required, rules such as compatibility and inclusion, etc.), and data input becomes more complicated There was a problem that it was not easy.

  An object of the present invention is to provide a database creation system capable of easily inputting data for a database even if there is a parent-child relationship between data.

(1) To achieve the above object, the present invention, the input data, a database creation system to be registered in the database as data in the table configuration can be registered in the database, the input data, each the column is data tabular data is written in each row, for the data of Table format each row to each other have a parent-child relationship, the parent-child relationship in the column direction of the data of said tabulated, the A first including hierarchical level information such that one column is a first hierarchy, a second column is a second hierarchy lower than the first hierarchy, and a third column is a third hierarchy lower than the second hierarchy . of adding header information, based on the first header information, the data of said tabulated, which is registered in the database as data in the table structure that can be registered in said database, said table The generated data describes the items of number, name, hierarchy level, and parent ID in the column direction, and each data in the row direction. The numbers are consecutively assigned numbers. When the table format data is the data of the table configuration, when the data of the first hierarchy of the table format data is described in the data item, the hierarchy level is 1, and the parent level When ID = 0 and second level data of the tabular data is described in the data item, the hierarchical level is 2, the parent ID is the number of the parent data, and the table When the data of the third hierarchy of the format data is described in the data item, the hierarchy level is 3, and the ID of the parent is the number of the parent data .
With this configuration, database data can be easily input even if there is a parent-child relationship between the data.

In (2) above (1), preferably, with respect to the tabular data each row to each other have a parent-child relationship, further adds a second header information indicating a combination relationship between the data, said The second header information is added to the first row of the tabular data, has a hierarchical level information for each row, and is different from the first data group designated by the first header information. The data of the second data group is sequentially described in a column following the second header information, specified by the first header information, and in the row direction. and written data, the specified in the second header information, the intersection of the matrix of data described in the column direction, define the rules of combination between the data and the first header information, wherein Second header information and the matrix Based on the rules of the intersection combination relationships, the data of the table-format, in which be registered in the database as a data table configuration that can be registered in the database.

( 3 ) In the above ( 2 ), preferably, the rule of the combination between the data is whether or not the data of the first data group and the data of the second data group are compatible. And an include rule that includes the data of the second data group with respect to the data of the first data group .

( 4 ) In the above (1), preferably, information having a parent-child relationship is displayed or selected using data registered in the database.

  According to the present invention, it is possible to easily input data for a database even if there is a parent-child relationship between the data.

Hereinafter, the configuration and processing operation of a database creation system according to an embodiment of the present invention will be described with reference to FIGS.
First, the system configuration of the database creation system according to the present embodiment will be described with reference to FIG.
FIG. 1 is a system block diagram showing a configuration of a database creation system according to an embodiment of the present invention.

  The input data of the database creation system 10 includes sheet format data D1. The data D1 is data created by using spreadsheet software, and is tabular data, for example, data described in CSV format. The data structure of the sheet format data D1 will be described later with reference to FIGS. The sheet format data D1 may be a single sheet or a plurality of sheets.

  The database creation system 10 inputs the parent-child relationship sheet data D1 option rule sheet data D2, generates a parent-child relationship and a mutual relationship for these data, and then sets the data format to be registered in the database (DB) 20. Convert and register in the database 20.

  The user can access the database 20 via the Internet using the Web terminal device 30 and the like, and can display data registered in the database 20 on the display screen of the Web terminal device 30. As the display format, for example, a tree format (left side of the lower left display example in FIG. 1) or a drill down format (right side of the lower left display example in FIG. 1) can be selected. As a result, it is possible to display in a tree format or select predetermined data in a drill-down format.

Next, processing contents of the database creation system according to the present embodiment will be described with reference to FIG.
FIG. 2 is a flowchart showing the processing contents of the database creation system according to the embodiment of the present invention.

  First, a process for generating a parent-child relationship for data will be described with reference to FIG. In this process, steps s50, s60, s70, and s80 are not executed. Therefore, these processes will be described later in the correlation generation process.

  First, in step s10, the database creation system 10 reads the sheet format data D1 as, for example, a CSV file. Here, for simplicity of explanation, the number of sheets is one. When there are a plurality of sheets, in step s20, the database creation system 10 executes a process of dividing the read sheet format data D1 for each sheet.

  Next, in step s30, the database creation system 10 generates a parent-child relationship for the sheet data of the read sheet format data D1.

Here, an example of sheet format data D1 read by the database creation system 10 and data in which a parent-child relationship is generated for the sheet format data D1 will be described with reference to FIG.
FIG. 3 is an explanatory diagram illustrating an example of data obtained by the data reading process and the parent-child relation generation process of the database creation system according to the embodiment of the present invention.

  In the tabular data shown in FIG. 3, the first to fourth lines are data (parent-child relationship header information) added in the parent-child relationship generation processing. The fifth and subsequent lines are sheet data of the sheet format data D1 read by the database creation system 10.

  First, the original data will be described. Here, an example of a notebook computer is shown. The example of the fifth row indicates that there is a model “A4 model 1” for “note type” and “A4 size”. Similarly, the sixth line indicates that there is a model “A4 model 2”.

  For such tabular data, the database creation system 10 adds header information indicating the attributes of each column including parent-child relationship information to the first to fourth rows, and uses this header information for parent-child relationship. Is generated.

  The header information is composed of “#table_name” on the first line, “#field_name” on the second line, “#relation” on the third line, and “#set_level” on the fourth line, These definition files are arranged in the first column (1A, 2A, 3A, 4A) of each row.

  In “#table_name” on the first line of the header information, the table name of the database created by the data on and after the fifth line is defined. Here, “table1” is described in each column after the first row, second column, and it is defined that a table “table1” is generated.

  In “#field_name” on the second line of the header information, a field name in the table is defined. Here, the data described in the 2nd, 3rd and 4th columns indicates a name (name), and the data “note type”, “A4 size”, and “A4 model 1” are names. Is shown.

  “#Relation” in the third row of the header information indicates an attribute indicating a relationship with the data in the left adjacent column. That is, the third row and the second column (3B) indicate “root”, thereby indicating that the second column is “parent”. In addition, the third row, the third column, and the fourth column in the same row are described as “child”, so that the left adjacent column (the third column is for the second column and the fourth column is for the third column ) Indicates "child".

  “#Set_level” in the fourth line of the header information indicates a hierarchical level indicating a parent-child relationship. Since the second column is “parent”, the hierarchy level is “1”. For this parent, the hierarchy level of each “child” is shown. In other words, the third column indicates that the data is arranged at a hierarchy level “2” and arranged one hierarchy below the “parent”. Further, the fourth column indicates that the data is arranged at the hierarchy level “3” and arranged two layers below the “parent”.

  As described above, in the parent-child relationship generation process in step s30, the first to fourth lines in FIG. 3 are applied to the sheet format data D1 (from the fifth line in FIG. 3) read by the database creation system 10. The header information indicating the attribute of each column shown in is added.

  Next, in step s60 of FIG. 2, the database creation system 10 confirms the parent-child relationship of the data to which the parent-child relationship is added, and when the parent-child relationship is confirmed, converts it into data to be registered in the database 20, step s90. In FIG.

Here, the parent-child relationship of the data to which the parent-child relationship shown in FIG. 3 is added and the data configuration registered in the database 20 will be described with reference to FIG.
FIG. 4 is an explanatory diagram showing an example of data obtained by the parent-child relationship confirmation processing and registration processing of the database creation system according to the embodiment of the present invention. 4A shows a parent-child relationship diagram, and FIG. 4B shows table information registered in the database.

  In the parent-child relationship confirmation process, the database creation system 10 determines whether or not a tree-structure parent-child relationship diagram is established based on the parent-child relationship attribute header shown in FIG. 3 as shown in FIG. Check whether the parent-child relationship has been granted normally.

  When the parent-child relationship is confirmed, the database creation system 10 creates the table information shown in FIG. 4B using the data shown in FIG. As shown in FIG. 4B, the table information registered in the database 20 includes “ID”, “name”, “level”, and “Parent_id”. “ID” is composed of a unique number or the like for identifying each data. For example, as shown in FIG. 4B, “ID” is a consecutive number of “1”, “2”, and “3”. “Name” is the name of “name” shown in FIG. The names are, for example, “note type”, “A4 size”, “A4 model 1”, “A4 model 2” based on FIG. “Level” indicates the hierarchy of “#set_level” shown in FIG. For example, “note type” has a hierarchy “1”, “A4 size” has a hierarchy “2”, and “A4 model 1” has a “hierarchy 3”. “Parent_id” describes the “ID” of the parent of the parent-child relationship. Since the parent of “A4 size” is “note type”, “1” which is “ID” of “note type” is attached. Since the parent of “A4 model 1” is “A4 size”, “2” which is “ID” of “A4 size” is attached.

Next, the contents of the option categorization generation process in step s40 of FIG. 2 will be described using FIG. 2 and FIG.
FIG. 5 is an explanatory diagram of an example of data obtained by the option categorization generation process of the database creation system according to the embodiment of the present invention.

  In step s40 of FIG. 2, the database creation system 10 generates data obtained by subjecting the sheet format data D1 read into the database creation system 10 to option categorization. Option categorization is one of the relative relationships between data, and is an index indicating whether or not combinations between data are possible, such as “combination is impossible” or “combination required” between data.

  In the tabular data shown in FIG. 5, the second and fourth columns after the eighth row are the second sheet data of the sheet format data D <b> 1 read by the database creation system 10. In this example, in addition to the first sheet data shown in FIG. 3, there is the second sheet data shown in FIG. 2, the sheet format data D1 including the data in FIGS. 3 and 5 is divided into two sheets in FIGS. 3 and 5 respectively. For the first sheet data, a parent-child relationship is generated as described with reference to FIG.

  On the other hand, the data shown in FIG. 5 is subjected to parent-child relationship generation processing and option categorization generation processing.

  First, the content of the second sheet data of the sheet format data D1 read by the database creation system 10 will be described. Here, an example of a notebook computer is also shown. In the example of the eighth row, “internal unit” indicates that there is a CPU of “P3 1.8 GHz” with respect to “CPU”. Similarly, the ninth line indicates that “internal unit” is “P3 2.0 GHz” CPU with respect to “CPU”.

  For such tabular data, the database creation system 10 adds the parent-child relationship header information indicating the attribute of each column to the third to seventh rows, and generates the parent-child relationship based on this header information. ing.

  The header information includes “#table_name” on the third line, “#field_name” on the fourth line, “#relation” on the fifth line, “#set_level” on the sixth line, It is composed of “#matrix” on the line, and these definition files are arranged in the first column of each line. These items are the same as those in FIG.

  In “#table_name” on the third line of the header information, the table name of the database created by the data on and after the eighth line is defined. Here, “table1” is described in the third row, the second, third, and fourth columns to define that a table “table1” is generated.

  In “#field_name” on the fourth line of the header information, a field name in the table is defined. Here, the data described in the second, third, and fourth columns indicates a name (name), and the data “internal unit”, “CPU”, and “P3 1.8G” are names. Is shown.

  “#Relation” in the fifth row of the header information indicates an attribute indicating a relationship with the data in the left adjacent column. That is, the fifth row and the second column (5B) indicate “child”, thereby indicating that the second column is “child”. Further, the fifth row, third column (5C), and the fourth row (5D) of the same row also indicate that they are “children” on the left side.

  “#Set_level” on the sixth line of the header information indicates the hierarchical level of the parent-child relationship. As shown in FIG. 3, when the hierarchy level of “parent” is “1”, the hierarchy level of each “child” for this parent is shown. In other words, the second column indicates that the data is arranged at the hierarchy level “4” and arranged under the “parent” three layers. Further, the fourth column indicates that the data is arranged at the hierarchy level “5”, which is arranged under the four layers of “parent”. Further, the sixth column indicates that the data is arranged at the hierarchy level “6” and arranged under the “parent” five layers.

  “Matrix” in the seventh line of the header information indicates that there is matrix data for option categorization described later.

  As described above, a parent-child relationship is generated by the parent-child relationship generation processing header information in the third to seventh lines by the parent-child relationship generation processing.

  Further, in the option categorization generation process, first and second lines are added as header information for the categorization generation process.

  The header information for categorization generation processing includes “#table_name” in the fifth column (1E) of the first row, “#field_name” in the sixth column (1F) of the first row, and the seventh column (1G of the same row). ) “#Relation”, “#set_level” in the eighth column (1H) of the same row, and “#matrix” in the ninth column (1I) of the same row.

  In “#table_name” of the header information for categorization generation processing, the table name of the database created by the data in the second column and the fifth column is defined. Here, “table1” is described in the second row and fifth column to define that a table “table1” is generated. This table is the same table as the table created by the first sheet data shown in FIG.

  In “#field_name” of the header information, a field name in the table is defined. Here, the data described in the second row, the 10th and 11th columns (2J, 2K) indicates that the name is “name”, and the data “A4 model 1” and “A4 model 2” are the names. It shows that there is.

  “#Relation” in the header information indicates whether the data in the second row is “parent” or “child” in the parent-child relationship, and whether the data is paired with the previous column. That is, the second row and sixth column (2F) indicates “child” by describing “child”.

  “#Set_level” in the header information indicates the hierarchical level of the parent-child relationship. As shown in FIG. 3, when the hierarchical level of “parent” is “1”, the hierarchical level of each “child” for this parent is shown. That is, the second row indicates that the data is arranged at the hierarchy level “3” and arranged under the two layers of “parent”. This hierarchical level is the same as the data of the hierarchical level “3” shown in FIG.

  Further, the option categorization between the hierarchy level “3” and the hierarchy level “6” is added to the intersection of the matrix by a code (“0”, “1”, “2”, “blank”). For example, the intersection (8J) between “A4 model 1” of the hierarchy level “3” and “P31.8 GHz” of the hierarchy level “6” is appended with “2”, and the “A4 model of the hierarchy level“ 3 ” “0” (9J) is added to the intersection of “1” and “P32.0 GHz” of the hierarchy level “6”.

  Here, the symbol “0” indicates “combination is impossible”, the symbol “1” indicates “standard”, the symbol “2” indicates “essential”, and the symbol “blank” indicates “combination is possible”. . That is, for “A4 model 1” of the hierarchy level “3”, the CPU of “P31.8 GHz” of the hierarchy level “6” is the “essential” combination, and the “A4 model 1” of the hierarchy level “3”. ”, The CPU of“ P32.0 GHz ”at the hierarchy level“ 6 ”is set to“ uncombinable ”. Similarly, for “A4 model 1” of the hierarchy level “3”, the memory of “512 MB” of the hierarchy level “6” is set to the combination of “standard” (10J), and “ For “A4 model 1”, the memory of “1024 MB” at the hierarchy level “6” is set to “combinable” (11J).

  In this way, by adding information (for optional categorization) on the possibility of the combination of the two at the intersection of the matrix, it is possible to combine the two data, whether it is a standard combination, or impossible to combine Combination information such as whether or not there is an essential combination can be provided.

  As described above, the option categorization information is generated by the option categorization generation process from the parent-child relationship generation process header information in the third to seventh rows and the information of the intersection of the two data matrices.

  Next, in step 70 of FIG. 2, the database creation system 10 confirms the categorization relationship of the added data for option categorization, and when this interphase relationship is confirmed, converts it into data to be registered in the database 20, In step s90, registration is made in the database 20.

Here, the parent-child relationship of the data added with the option categorization shown in FIG. 4 and the data configuration registered in the database 20 will be described with reference to FIG.
FIG. 6 is an explanatory diagram of an example of data obtained by the option categorization confirmation process and registration process of the database creation system according to the embodiment of the present invention. 6A shows a parent-child relationship diagram, and FIG. 6B shows table information registered in the database.

  In the confirmation processing for option categorization, the database creation system 10 determines whether or not a parent-child relationship diagram having a tree structure is established as shown in FIG. 6A based on the parent-child relationship attribute header shown in FIG. Check whether the parent-child relationship has been granted normally.

  When the parent-child relationship is confirmed, the database creation system 10 creates table information shown in FIG. 6B using the data shown in FIG. As shown in FIG. 6B, the table information registered in the database 20 includes “ID”, “name”, “level”, and “Parent_id”. “ID” is composed of a unique number or the like for identifying each data. For example, as shown in FIG. 4B, “ID” is a consecutive number of “1”, “2”, and “3”. “Name” is the name of “name” shown in FIG. Each name is based on FIGS. 3 and 5, for example, “note type”, “A4 size”, “A4 model 1”, “A4 model 2”, “internal unit”, “external unit”, “CPU”. , “Memory”, etc. “Level” indicates the hierarchy of “#set_level” shown in FIG. For example, “note type” has a hierarchy “1”, “A4 size” has a hierarchy “2”, and “A4 model 1” has a “hierarchy 3”. “Parent_id” describes the “ID” of the parent of the parent-child relationship. Since the parent of “A4 size” is “note type”, “1” which is “ID” of “note type” is attached.

  Further, as a relation of the information for option categorization, “name” is the name of “name” shown in FIG. Each name is, for example, “internal unit”, “external unit”, “CPU”, “memory” based on FIG. “Level” indicates the hierarchy of “#set_level” shown in FIG. For example, “internal unit” and “external unit” are layer “4”, “CPU”, “memory” are layer “5”, and “P3 1.8G” is “layer 6”. “Parenet_id” describes “ID” of the parent of the parent-child relationship. Since the parent of “internal unit” is “A4 model 1” and “A4 model 2”, “4” and “5” which are “ID” of “A4 model 1” and “A4 model 2” are attached. ing.

Next, the contents of the inter-option rule generation process in step s50 of FIG. 2 will be described using FIG. 2 and FIG.
FIG. 7 is an explanatory diagram showing an example of data obtained by the inter-option rule generation processing of the database creation system according to the embodiment of the present invention.

  In step s50 of FIG. 2, the database creation system 10 generates data in which the inter-option rule is applied to the sheet format data D1 read by the database creation system 10. The rule between options is one of the relative relationships between data, and is a rule between data such as a “compatibility” rule or an “include” rule between data. Here, the “compatibility” rule is a rule indicating whether or not data can be attached between a plurality of data by exclusive control. For example, the part A indicated by the data A indicates whether or not the part B indicated by the data B is attached. The “include” rule is a rule that when another data (for example, part B) is attached to a certain data A (for example, part A), other data (for example, part C) is automatically attached.

  In the tabular data shown in FIG. 7, the second column is the third sheet data of the sheet format data D <b> 1 read by the database creation system 10 after the seventh row. In this example, in addition to the first sheet data shown in FIG. 3 and the second sheet data shown in FIG. 5, there is the third sheet data shown in FIG. Then, in the sheet-by-sheet division processing in step s20 in FIG. 2, the sheet format data D1 including the data in FIGS. 3, 5, and 7 is divided into the three sheets in FIGS. 3, 5, and 7, respectively. For the first sheet data, a parent-child relationship is generated as described with reference to FIG. Further, as described with reference to FIG. 5, the parent-child relationship generation process and the option categorization generation process are performed on the second sheet data.

  Furthermore, an inter-option rule generation process is performed on the data shown in FIG.

  First, the contents of the third sheet data of the sheet format data D1 read by the database creation system 10 will be described. Here, an example of a notebook computer is also shown. In the example of the second column (7B, 8B, 9B, 10B) in the seventh to tenth rows, “512 MB”, “1012 MB” memory, “printer”, “cable” are the parts to which the rule between options is applied. This indicates that there are printer parts.

  The database creation system 10 adds header information indicating the attribute of each column to the third to sixth rows with respect to such tabular data.

  The header information is composed of “#sheet_name” on the third line, “#table_name” on the fourth line, “#field_name” on the fifth line, and “#matrix” on the sixth line. These definition files are arranged in the first column of each row.

  “#Sheet_name” on the third line of the header information indicates a range (category setting sheet) to which the inter-option rule shown in FIG. 7 is applied. In this example, the category setting sheet is FIG. 5, and the sheet name is “A4Note”. Therefore, the application range of the rule shown in FIG. 7 is “A4 model 1” and “A4 model 2”.

  In “#table_name” on the fourth line of the header information, a table name in the table is defined. Here, the data described in the second column is “option”, and defines that a table “option” is generated.

  In “#field_name” on the fifth line of the header information, a field name in the table is defined. Here, the data described in the 5th row and the 2nd column indicates an option name (opt_name), which is referred to as “512 MB”, “1012 MB”, “printer”, and “cable” in the seventh row and thereafter. Indicates that the data is an option name.

  “Matrix” in the sixth line of the header information indicates that there is matrix data for an option rule to be described later.

  Further, in the inter-option rule generation process, first, the first and second lines are added as header information for the inter-option rule generation process.

  The header information for inter-option rule generation processing includes “#table_name” in the third column (1C) of the first row, “#field_name” in the fourth row (1D) of the first row, and the fifth row of the same column. (1E) “#matrix”.

  Here, the fourth row and second column (4B) and the second row and third column (2C) in the table shown in FIG. 7 are the same, and the fifth row and second column (5B) and the second row and fourth column (2D) are 6th row and 2nd column (6B) and 2nd row and 5th column (2E) are the same, 7th row and 2nd column (7B) and 2nd row and 6th column (2F) are the same The eighth row and the second column (8B) and the second row and the seventh column (2G) are the same, the ninth row and the second column (9B) and the second row and the eighth column (2H) are the same, and the tenth row The second column (10B) and the second row and ninth column (2I) are the same. That is, a matrix for the same combination of data is formed by the 7th to 10th rows in the second column and the 6th to 9th rows in the second row.

  Then, the inter-option rules for these data are added to the intersection of the matrix by a code (“1”, “2”, “blank”). For example, “1” is added to the intersection (7G) between the memory of “512 MB” and the memory of “1012 MB”, and “2” is added to the intersection (10H) of “printer” to “cable”. Is done.

  Here, the symbol “1” indicates the “compatibility” rule described above, the symbol “2” indicates the “include” rule described above, and the symbol “blank” indicates “no rule”. That is, the “512 MB” memory and the “1012 MB” memory have “compatibility”, and when the “512 MB” memory is attached, the “1012 MB” memory cannot be attached. . In addition, “printer” is “include” with respect to “cable”, and it is necessary to attach “printer” together to attach “cable”.

  In this way, by adding a rule (a rule between options) at the time of combination of the two to the intersection of the matrix, it is possible to have information on compatibility rules and include rules of the two data.

  As described above, the inter-option rule information is generated from the header information of the third to sixth lines, the header information of the first and second lines, and the information of the intersection of the two data matrixes by the inter-option rule generation process. The

  Next, in step 80 of FIG. 2, the database creation system 10 confirms the inter-option rule relationship of the data to which the inter-option rule is added, and when this inter-phase relationship is confirmed, converts it into data to be registered in the database 20. In step s90, it is registered in the database 20.

Here, with reference to FIG. 8, the relationship between the data to which the rule between options shown in FIG. 4 is added and the data configuration registered in the database 20 will be described.
FIG. 8 is an explanatory diagram showing an example of data obtained by the inter-option rule checking process and the registration process of the database creation system according to the embodiment of the present invention. FIG. 8A shows a rule relation diagram, and FIG. 8B shows table information registered in the database.

  In the inter-option rule confirmation process, the database creation system 10 determines whether the rule relationship is based on whether or not a tree structure relationship diagram is established, as shown in FIG. 8A, based on the attribute header shown in FIG. Check whether it has been granted normally.

  When the rule relationship is confirmed, the database creation system 10 uses the data shown in FIG. 7 to extract a portion to which a code is attached from the matrix of FIG. 7, and to create a table as shown in FIG. Create Next, the database creation system 10 creates table information shown in FIG. 8C from the table in FIG. 8B and registers it in the database 20. The table of FIG. 8C extracts “ID” described in “table1” from the vertical option name in the table of FIG. 8B and sets it to “ID_x” of FIG. 8C. Similarly, “ID” is extracted from the option name in the horizontal direction, and set to “ID_y” in FIG. The extracted code is set to “Rule_id”.

  As described above, a large number of data can be input easily by using tabular data generated by spreadsheet software or the like.

  When there is a parent-child relationship between the data, the parent-child relationship can be easily defined by defining header information at a hierarchical level indicating the parent-child relationship in the tabular data. Then, the data for the database can be generated using the hierarchical level indicating the parent-child relationship. Therefore, even when the configuration of the database is changed, it is not necessary to rearrange the tabular data again, and the configuration of the database can be easily changed.

  Also, by adding header information for option categorization of the combination relationship between two data (possibility of combination) and defining the combination relationship at the intersection of the matrix between two data, Data for a database can be easily generated.

In addition, by defining rules such as compatibility and inclusion between two data options at the intersection of the matrix between the two data, it is easy to generate database data for data with rules. can do.

It is a system block diagram which shows the structure of the database creation system by one Embodiment of this invention. It is a flowchart which shows the processing content of the database creation system by one Embodiment of this invention. It is explanatory drawing of an example of the data obtained by the data reading process of the database creation system by one Embodiment of this invention, and a parent-child relationship generation process. It is explanatory drawing of an example of the data obtained by the parent-child relationship confirmation process and registration process of the database creation system by one Embodiment of this invention. Note that FIG. It is explanatory drawing of an example of the data obtained by the option categorization production | generation process of the database creation system by one Embodiment of this invention. It is explanatory drawing of an example of the data obtained by the confirmation process for option categorization of a database creation system by one Embodiment of this invention, and a registration process. It is explanatory drawing of an example of the data obtained by the rule creation process between options of the database creation system by one Embodiment of this invention. It is explanatory drawing of an example of the data obtained by the rule confirmation process between options of a database creation system by one Embodiment of this invention, and a registration process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Database creation system 20 ... Database 30 ... Web terminal device

Claims (4)

A database creation system that registers input data in the database as data of a table configuration that can be registered in the database,
The input data is tabular data in which data is described for each row in each column .
For the tabular data in which each column has a parent-child relationship, the parent-child relationship in the column direction of the tabular data is that the first column is the first hierarchy and the second column is lower than the first hierarchy. The first header information including the information of the hierarchy level is added so as to be the second hierarchy, and the third column is the third hierarchy lower than the second hierarchy ,
Based on the first header information, the tabular data is registered in the database as table configuration data that can be registered in the database.
In the data of the table configuration, each item of the number, name, hierarchical level, and parent ID is described in the column direction, and each data is described in the row direction. The numbers are consecutively assigned numbers. And
When the data in the table format is the data of the table configuration,
When the data of the first hierarchy of the tabular data is described in the data item, the hierarchy level is 1 and the parent ID = 0,
When describing the data of the second hierarchy of the tabular data in the data item, the hierarchy level is 2, and the ID of the parent is the number of the parent data,
When the data of the third hierarchy of the tabular data is described in the data item, the hierarchy level is 3, and the parent ID is the number of the parent data. A database creation system characterized by The database creation system according to claim 1,
With respect to the tabular data having the respective rows with each other parent-child relationship, further adds a second header information indicating a combination relationship between the data,
The second header information is added to the first row of the tabular data, has hierarchical level information for each row, and is different from the first data group specified by the first header information. Generated for a second data set,
The data of the second data group is sequentially described in a column following the second header information,
The specified in the first header information, and data described in the row direction, as specified in the second header information, the intersection of the matrix of data described in the column direction, the rule of combination between the data Define
Based on the rule of the relationship between the first header information, the second header information, and the intersection of the matrix, the tabular data is stored in the database as table-structured data that can be registered in the database. A database creation system characterized by registration. The database creation system according to claim 2,
The combination rule between the data includes a compatibility rule as to whether or not the data of the first data group and the data of the second data group are compatible, and the data of the first data group. A database creation system comprising an include rule that also includes data of the second data group. The database creation system according to claim 1,
A database creation system for displaying or selecting information having a parent-child relationship using data registered in the database.

Images