JP2009104276A - Data management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data management device quickly retrieve data with a simple configuration. <P>SOLUTION: This data management device storing data included in an XML (eXtensible Markup Language) document has: a storage execution part 18 sorts each data in the XML document to expansion data to be stored in undecided data structure or basic data to be stored in a preset data structure based on a storage rule of the data, storing the basic data in a basic data storage DB 23, and storing the expansion data in an expansion data storage DB 24; a storage location information storage part 20 storing a position to store each expansion data and a position to store each basic data as storage location management information; and a retrieval processing part 15 retrieving the expansion data and the basic data corresponding to a retrieval request from the expansion data storage DB 24 and the basic data storage DB 23 based on the storage location management information. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a data management apparatus that selectively uses a database that stores a data portion in accordance with the data portion to be managed.

  In recent years, with the enhancement of functions of embedded devices such as car navigation devices and mobile phones, development of easy-to-use databases used in embedded devices has been promoted. In such a database, for example, it is desired that various data can be efficiently stored, and that desired data can be quickly retrieved from the database. However, in order to realize high-speed search processing in embedded devices, if data to be stored is determined in advance, such as an RDB (Relational Data Base) table that specifies the data structure, extended data is added later to store the data. There was a problem that I could not do it.

  The data conversion system described in Patent Document 1 converts only a portion to be used from XML (eXtensible Markup Language) data including a schema structure into a relational format and stores it in the RDB.

  The database model described in Patent Document 2 maps descriptors and their hierarchical descriptors to a relational database management system for XML documents or the like having a hierarchical data format.

JP 2006-1114045 A JP 2006-501539 A

  However, in the former and the latter prior art, when an XML document is stored in the RDB on an embedded device having a low CPU (Central Processing Unit) capability and a small amount of memory compared to a PC (Personal Computer), the embedded device is stored in the RDB. There was a problem that stored data could not be searched at high speed.

  In addition, as in the latter prior art, when an RDB mapping XML-DB is installed in a device and an XML document that easily has extended data is stored in the database, it is compared with an RDB that stores only necessary data in advance. Since extra information is stored in the database, there is a problem that the search process is slow.

  The present invention has been made in view of the above, and an object of the present invention is to obtain a data management apparatus capable of quickly retrieving desired data with a simple configuration.

  In order to solve the above-described problems and achieve the object, the present invention divides data contained in an XML document and stores the divided data in a relational database or an XML database. Based on the storage rules relating to the storage location of the data, each data in the XML document is set to basic data to be stored in a predetermined data structure set in advance or extended data in which the data structure of the storage destination is not determined, A storage execution unit for storing the basic data in the relational database and storing the extended data in the XML database, a position in the relational database in which the basic data is stored, and the extended data are stored. The location in the XML database When there is a storage location storage unit that stores information and a search request for the data, based on the storage location management information, basic data and extended data corresponding to the search request are retrieved from the relational database and the XML database. A search processing unit for searching.

  According to the present invention, since the position in the relational database in which each basic data is stored and the position in the XML database in which each extended data is stored are stored, desired data can be searched quickly with a simple configuration. There is an effect.

  Embodiments of a data management apparatus according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram showing a configuration of a data management apparatus according to Embodiment 1 of the present invention. The data management device 1 is a device (hybrid database system) disposed in an embedded device such as a car navigation device or a mobile phone.

  The data management apparatus 1 according to the present embodiment includes a basic data portion (data to be stored in a predetermined data structure) that can store an XML document in a predetermined structure, and an extended data portion that cannot be stored in a predetermined structure. (Data for which the data structure of the storage destination is not determined) is automatically divided and stored in the RDB (basic data storage DB 23) and the RDB mapping XML-DB (extended data storage DB 24), respectively.

  In the present embodiment, for example, data that is commonly used by devices equipped with the data management apparatus 1 (data that is frequently searched) is set as basic data, and is included in the category of basic data depending on the use of the XML document. Unusable data is set as extended data.

  In the data management apparatus 1, an optimal schema for an embedded device is devised, and an RDB or RDB mapping XML-DB is designed. Thereby, the data management apparatus 1 searches the basic data part and the extended data part stored in the RDB or RDB mapping XML-DB at high speed.

  As shown in FIG. 1, the data management apparatus 1 includes a search request input unit 11, a search result output unit 12, a storage rule input unit 13, a data input unit 14, a search processing unit 15, a storage rule storage unit 16, and a storage rule determination. A processing unit 17, a storage execution unit 18, a storage location management unit 19, a storage location information storage unit (storage location storage unit) 20, a basic data search unit 21, an extended data search unit 22, a basic data storage DB 23, and an extended data storage DB 24 I have.

  The search request input unit 11 inputs a search condition for data to be searched and sends it to the search processing unit 15. The search result output unit 12 receives the data (search result) searched by the basic data search unit 21 and the extended data search unit 22 via the search processing unit 15 and outputs the data to an external device or the like.

  The storage rule input unit 13 inputs information related to a database schema generation instruction (storage rule condition information 101 described later) and sends the information to the storage rule determination processing unit 17. The data input unit 14 inputs document data (document 103 described later) (XML document) to be stored in the data management apparatus 1 and sends it to the storage execution unit 18.

  The storage execution unit 18 analyzes the document 103 sent from the data input unit 14 to extract data of each layer, and inquires of the storage rule determination processing unit 17 about the storage location of the extracted data. The storage execution unit 18 determines that the data for which the storage destination is inquired is the basic data when the storage destination of the inquired data is in the storage destination information table 102 described later.

  When the storage execution unit 18 receives storage destination information (table ID and column ID that is a storage destination of basic data) from the storage rule determination processing unit 17 as a data storage destination, the storage execution unit 18 is designated by the table ID from within the basic data storage DB 23. The basic data storage table is searched, and the column specified by the column ID is searched from the extracted basic data storage table. The storage execution unit 18 stores the basic data of the document 103 in the column in the found basic data storage table.

  When storing new data in the basic data storage DB 23, the storage execution unit 18 generates a storage destination (basic data entry ID, table ID, which will be described later) for storing a new basic data row, and the data of the document 103. Remember until storage is complete.

  When the storage destination of the inquired data is not in the storage destination information table 102, the storage execution unit 18 determines that the data for which the storage destination is inquired is extended data. When the storage execution unit 18 determines that the data for which the storage destination is inquired is extension data, the storage execution unit 18 associates the stored table ID and the basic data entry ID with the extension data for which the storage destination is inquired. When the data to be stored is extended data, the storage execution unit 18 generates an information table for storing extended data (extended data storage table 105 described later) in the extended data storage DB 24, and stores the information table in the generated extended data storage DB 24. Stores extended data.

  When the storage rule determination processing unit 17 receives the storage rule condition information 101 from the storage rule input unit 13, it instructs the storage destination management unit 19 to generate a database schema according to the storage rule condition information 101.

  Further, when there is an inquiry about the storage destination of the data (document 103) from the storage execution unit 18, the storage rule determination processing unit 17 causes the storage destination management unit 19 to inquire about the data storage destination (storage destination information). When the storage rule determination processing unit 17 receives the table ID and the column ID as the storage destination of the basic data from the storage destination management unit 19 as the storage destination information (inquiry result), it passes these storage destination information to the storage execution unit 18. .

  Upon receiving a database schema generation instruction from the storage rule determination processing unit 17, the storage location management unit 19 generates a storage location information table 102 based on the storage rule condition information 101 and stores it in the storage location information storage unit 20. Further, the storage location management unit 19 generates an information table (basic data storage table 104 described later) in the basic data storage DB 23 based on the storage location information table 102.

  When the storage rule determination processing unit 17 inquires about the storage destination of the data, the storage destination management unit 19 determines whether or not the corresponding storage destination information exists in the storage destination information storage unit 20. The storage location management unit 19 searches the storage location information table 102 for conditions that match the hierarchy of the inquired data. If there is storage location information corresponding to the inquired data in the storage location information storage unit 20, the storage location management unit 19 determines that the inquired data is basic data, and sends it to the storage rule determination processing unit 17. The table ID and column ID of the information table that is the storage destination of the basic data are sent.

  The storage rule storage unit 16 is a storage unit such as a memory that stores the storage rule condition information 101 received by the storage rule determination processing unit 17 via the storage rule input unit 13. The storage location information storage unit 20 is a storage unit such as a memory that stores the storage location information table 102 generated by the storage location management unit 19.

  When receiving the search condition from the search request input unit 11, the search processing unit 15 inquires the storage destination management unit 19 about the data hierarchy corresponding to the search condition from the search request input unit 11 and sends it from the storage destination management unit 19. Whether basic data is searched first or extended data is searched first (whether it is basic data search or extended data search) based on the answer (storage location information regarding the data storage location) Judging.

  The search processing unit 15 determines that the basic data is searched first when storage destination information (basic data storage table name and column name, which will be described later) can be obtained from the storage destination management unit 19. The basic data search unit 21 is requested to search for basic data by passing storage location information and search conditions.

  When the basic data storage table name and the column name corresponding to the search condition cannot be acquired from the storage destination management unit 19, the search processing unit 15 determines that the extended data is searched first, and the extended data search unit 22. To search for extended data. When the search processing unit 15 requests the extension data search unit 22 to search for extension data, the search processing unit 15 uses storage location information (basic data storage table name and basic data entry ID described later) obtained by the search by the extension data search unit 22. It passes to the basic data search unit 21 and requests the basic data search unit 21 to search for basic data. The search processing unit 15 sends the data searched by the basic data search unit 21 and the extended data search unit 22 to the search result output unit 12.

  The basic data retrieval unit 21 retrieves basic data from the basic data storage DB 23 based on the storage location information and the retrieval conditions sent from the retrieval processing unit 15 and includes all the basic data entry IDs in the same row. Get column data. The basic data search unit 21 sends the acquired data to the search processing unit 15.

  When the basic data search unit 21 determines that the search condition sent from the search processing unit 15 is a condition that does not correspond to the stored basic data, the search condition is the search condition for the extended data. And the extended data search unit 22 is requested to search. The basic data search unit 21 determines that the search condition is a condition that does not correspond to the stored basic data when the storage destination information table 102 does not have a hierarchical condition indicating the data storage destination.

  The extension data search unit 22 searches the extension data storage DB 24 for extension data corresponding to the storage location information. Based on the storage location information sent from the search processing unit 15, the extended data search unit 22 acquires all data having the same basic data entry ID and the same basic data storage table name from the extended data storage DB 24. The extended data search unit 22 sends the acquired data (extension data, basic data storage table name, basic data entry ID) to the search processing unit 15.

  The basic data storage DB 23 is a database that stores the basic data storage table 104 generated by the storage destination management unit 19. The extended data storage DB 24 is a database that stores the extended data storage table 105 generated by the storage execution unit 18.

  Next, an operation procedure (data storage process and data search process) of the data management apparatus 1 will be described. FIG. 2 is a flowchart showing a data storage processing procedure. Storage rule condition information 101 is input in advance from the storage rule input unit 13 to the data management device 1. The storage rule input unit 13 stores (sets) the storage rule condition information 101 in the storage rule storage unit 16 (step S110).

  Here, the configuration of the storage rule condition information 101 will be described. FIG. 3 is a diagram illustrating an example of the storage rule condition information. FIG. 3 shows an example of the mounting specification of the storage rule condition information (storage rule condition formula) 101. The storage rule condition information 101 is information set by a user, and an XML document used in an embedded device or the like is divided into a basic data part common to all XML documents and an extended data part that differs depending on the use of the XML document. , Information regarding storage rules for division.

  For example, in the conditional expression on the first line in the figure, a column named “title” is provided in a table named “book-list”, and the hierarchy in the input document is “/ book / title /”. The node value in “” is stored. In this INPUT statement, what is described after TO is the basic data storage table name of the storage destination, and what is described after AS is the storage destination column name in the table. FIG. 3 shows a specification in which the order of the columns in the same table is determined in the order in which the conditional expressions are written.

  Next, the storage rule determination processing unit 17 instructs the storage destination management unit 19 to generate a database schema according to the storage rule condition information 101. Upon receiving a database schema generation instruction from the storage rule determination processing unit 17, the storage location management unit 19 generates a storage location information table 102 based on the storage rule condition information 101 and stores it in the storage location information storage unit 20 ( Step S120).

  In the storage location information table 102, any data portion of the XML document divided from the document 103 is stored in any position of the basic data storage DB 23, and any data portion of the XML document divided from the document 103 is stored as the extended data. This is information indicating in which position in the DB 24 the data is stored.

  Here, the configuration of the storage location information table 102 will be described. FIG. 4 is a diagram illustrating an example of the storage location information table. The storage location information table (storage location management information) 102 is an information table related to the data storage location in which the basic data storage table name, the column name, and the hierarchical path are associated with each other. In FIG. 4, for example, the basic data storage table name “book-list”, the column name “title”, and the hierarchical path “/ book / title /” are associated with each other.

  Next, the storage location management unit 19 generates the basic data storage table 104 in the basic data storage DB 23 based on the storage location information table 102 (step S130). Here, the configuration of the basic data storage table 104 will be described. FIG. 5 is a diagram illustrating an example of the configuration of the basic data storage table. The basic data storage table 104 is an information table related to basic data in which “basic data entry ID”, “title”, “title-kana”, “author”, and “author-kana” are associated with each other. FIG. 5 shows the configuration of the basic data storage table 104 whose basic data storage table name is “book-list”.

  “Basic data entry ID” is information for identifying an entry of data. “Title”, “title-kana”, “author”, and “author-kana” are column names indicating the title, the kana reading of the title, the kana reading of the author, and the author, respectively.

  In FIG. 5, the basic data whose “basic data entry ID” is “1” is that “title” is “Ryugu Castle Guidebook”, “title-kana” is “Ryugujo Guidebook”, and “author” Is “Taro Urashima” and “author-kana” is “Urashima Taro”.

  After the basic data storage table 104 is generated in the basic data storage DB 23, when the document 103 to be stored is input to the data input unit 14, this document 103 is sent to the storage execution unit 18 (step S140).

  Here, the configuration of the document 103 to be stored will be described. FIG. 6 is a diagram illustrating an example of a configuration of a document to be stored. In FIG. 6, the title of the document 103 is “Ryugu Castle Guidebook”, the reading of the title is “Ryugujo Guidebook”, the author is “Taro Urashima”, the author's reading of “Urashima Taro”, and the publisher (publisher) Is “Otogi Publishing”, and the international standard book number (isbn (International Standard Book Number)) is “123-1234567890”.

  The storage execution unit 18 analyzes the document 103 and extracts data of each layer (step S150), and inquires the storage rule determination processing unit 17 about the storage location of the extracted data. When there is an inquiry about the data storage destination from the storage execution unit 18, the storage rule determination processing unit 17 causes the storage destination management unit 19 to inquire about the data storage destination.

  When there is an instruction to inquire about the storage location of data from the storage rule determination processing unit 17, the storage location management unit 19 determines whether the corresponding storage location information is in the storage location information storage unit 20 (step S160). Specifically, the storage location management unit 19 searches the storage location information table 102 for a condition that matches the inquired data hierarchy.

  If storage destination information corresponding to the inquired data is stored in the storage destination information storage unit 20 (Yes in Step S160), the storage destination management unit 19 determines that the inquired data is basic data (Step S160). S170). Then, the storage destination management unit 19 extracts the table ID (ID for identifying the basic data storage table) and the column ID corresponding to the inquired data (hierarchical path) from the storage destination information table 102 (step S180). The table ID is an ID for identifying a basic data storage table such as the basic data storage table 104. The column ID is an ID for identifying the column name shown in the storage location information table 102.

  The storage location management unit 19 sends the table ID and column ID, which are the storage locations of the basic data, to the storage rule determination processing unit 17. When the storage rule determination processing unit 17 receives the table ID and column ID, which are the storage destinations of basic data, from the storage destination management unit 19, it sends the received table ID and column ID to the storage execution unit 18.

  When the storage execution unit 18 receives the table ID and the column ID from the storage destination management unit 19, the storage execution unit 18 determines that the data for which the storage destination is inquired is basic data. The storage execution unit 18 stores the basic data of the document 103 in the basic data storage table 104 in the basic data storage DB 23. Specifically, the storage execution unit 18 transfers the basic data to the column specified by the column ID extracted by the storage destination management unit 19 in the basic data storage table specified by the table ID extracted by the storage destination management unit 19. Is stored (step S190). At this time, the basic data storage DB 23 generates a new basic data row at the time of storage, and assigns a basic data entry ID to the generated data row.

  The storage execution unit 18 stores the basic data entry ID corresponding to the new basic data row and the table ID of the basic data storage table storing the new basic data until the data storage of the document 103 is completed. (Step S200).

  Thereafter, the storage execution unit 18 determines whether or not all the data extracted in the process of step S150 has been stored in the data management device 1 (basic data storage DB 23 or extended data storage DB 24) (step S210).

  When the storage execution unit 18 determines that all the data extracted in the process of step S150 is not stored in the data management apparatus 1 (No in step S210), the storage destination management unit 19 corresponds to the next data. It is determined whether the storage location information is in the storage location information storage unit 20 (step S160).

  When the storage destination management unit 19 determines that the storage destination corresponding to the inquired data is not in the storage destination information table 102 (No in step S160), the storage execution unit 18 uses the extended data as the data for which the storage destination is inquired. Judge. The storage execution unit 18 associates the basic data entry ID and the table ID stored in step S200 with the data for which the storage destination is inquired, and stores the data in the extended data storage DB 24. The storage execution unit 18 stores the extended data in the extended data storage table 105 in the extended data storage DB 24.

  The data management device 1 repeats the processing in steps S160 to S230 until all the data extracted in the processing in step S150 is stored in the data management device 1 (basic data storage DB 23 or extended data storage DB 24).

  FIG. 7 is a diagram showing the configuration of the extended data storage table. The extended data storage table 105 is an information table (node table) regarding extended data to which a hierarchical structure of nodes is added. In the extended data storage table 105, “node ID”, “parent node ID”, “hierarchy path”, “node name”, “node value”, “basic data storage table name”, and “basic data entry ID” are associated with each other. It has been.

  The “node ID” is information for identifying the node of the extension data, and the “parent node ID” is information (“node ID”) for identifying the parent node to which the extension data belongs. The “hierarchy path” is the hierarchy to which the extended data node belongs, and the “node name” is the node name of the extended data. The “node value” is the node value of the extended data, and the “basic data storage table name” is the table name of the table that stores the basic data. The “basic data entry ID” is information for identifying an entry of basic data.

  For example, the extension data having “node ID” “1” indicates that “parent node ID” is “0” and that the own node is the parent node. Further, the extension data having “node ID” “1” has “hierarchy path” “/ book /”. The “node name” is “book”, and the “node value” is none. Further, the “basic data storage table name” is “book-list”, and the “basic data entry ID” is “1”.

  In the present embodiment, the same entry ID (basic data) as the basic data divided and stored in the basic data storage table 104 is stored in all nodes from the root to the descendants of the extended data stored in the extended data storage table 105 in a tree structure. Entry ID) is associated. For example, since the nodes having node IDs “1” to “3” are nodes corresponding to the basic data stored in the basic data storage table 104, the same basic data entry ID “1” as the basic data is set. Correlate.

  In this embodiment, when the extension data is stored in the extension data storage DB 24, the extension data is associated with the basic data entry ID and the table ID stored in step S200. Until the table ID is extracted, the storage of the extension data is suspended and the storage process is performed from other basic data. In other words, until the first basic data is stored and the basic data entry ID and the table ID are obtained, the storage processing of the extended data in the extended data storage DB 24 is suspended.

  Next, a search process for data stored in the data management apparatus 1 will be described. FIG. 8 is a flowchart showing a data search processing procedure. When the search condition is input to the search request input unit 11, the search request input unit 11 sends the search condition to the search processing unit 15 (step S310).

  The search processing unit 15 analyzes the search condition from the search request input unit 11 and determines whether basic data is searched first or extended data is searched first. Specifically, the search processing unit 15 determines whether the search target is basic data or extended data based on whether the basic data storage table name and the column name can be obtained from the storage destination management unit 19. Judging. For example, when the search condition is / book / title / = “Ryugu Castle Guidebook”, the search processing unit 15 is a title whose title is “book” under the book and whose value is “Ryugu Castle Guidebook”. In order to acquire a set, the storage location management unit 19 is inquired about the hierarchy of / book / title /.

  The storage location management unit 19 extracts conditions (basic data storage table name and column name) that match the hierarchy inquired from the search processing unit 15 from the storage location information table 102 (step S320). For example, the storage location management unit 19 extracts the basic data storage table name “book-list” and the column name “title” from the storage location information table 102 as a condition that matches the hierarchy of / book / title /. The storage destination management unit 19 sends the extracted basic data storage table name and column name to the search processing unit 15.

  When the basic data storage table name and column name corresponding to the search condition (data hierarchy) can be acquired from the storage destination management unit 19 (Yes in step S330), the search processing unit 15 performs basic search processing. It is determined that the data is first (step S340). Then, the search processing unit 15 causes the basic data search unit 21 to store information related to the storage location in the storage location information table 102 (basic data storage table name “book-list” and column name “title”) and a search condition (= Send “Ryugu Castle Guidebook”).

  The basic data search unit 21 searches and acquires basic data corresponding to the search condition from the basic data storage DB 23. Specifically, the basic data search unit 21 searches the basic data from the basic data storage DB 23 based on the storage location information and search conditions sent from the search processing unit 15 and includes the basic data entry ID. Get data for all columns in the same row. As a result, the basic data search unit 21 acquires a data row corresponding to the basic data storage table name and the basic data entry ID from the basic data storage DB 23 (step S350). The basic data search unit 21 sends the acquired basic data to the search processing unit 15.

  Further, the search processing unit 21 sends the storage location information (basic data entry ID = “1” and the basic data storage table name “book-list”) in the basic data storage table 104 to the extended data search unit 22. The extension data search unit 22 searches and acquires extension data corresponding to the basic data searched by the basic data search unit 21 from the extension data storage DB 24. The extended data search unit 22 here uses the storage location information from the search processing unit 21 to acquire all the extended data whose basic data entry ID and basic data storage table name match from the extended data storage DB 24. Specifically, the extended data search unit 22 has a basic data storage table name corresponding to the basic data storage table name from the search processing unit 21 and basic data corresponding to the basic data entry ID from the search processing unit 21. The extension data having the entry ID is extracted from the extension data storage table 105 (step S360).

  The extended data search unit 22 sends the acquired data to the search processing unit 15. The search processing unit 15 sends the search results obtained from the basic data search unit 21 and the extended data search unit 22 to the search result output unit 12, and the search result is output from the search result output unit 12 (step S370).

  If the basic data storage table name and the column name corresponding to the search condition cannot be acquired from the storage destination management unit 19 (No in step S330), the search processing unit 15 performs the search with the extension data first. It is determined that there is (step S380). In other words, when the search condition input from the search request input unit 11 does not correspond to the basic data condition (hierarchical path) stored in the storage location information table 102, the search processing unit 15 uses the extended data as the basic data. It is determined that the search is performed before the data. For example, when a search for data (set) whose search condition is / book / isbn / = “123-1234567890” is requested (a data search where the level is “isbn” under “book” and the value is “123-12345567890”. The storage destination information table 102 does not have a hierarchical condition of / book / isbn /. For this reason, the search processing unit 15 determines that the search condition is extended data.

  Then, the search processing unit 15 requests the extension data search unit 22 to search for a condition of / book / isbn / = “123-12345567890”. The extended data search unit 22 searches the extended data storage DB 24 (extended data storage table 105) according to this search condition. As a result, the extended data search unit 22 can obtain the basic data storage table name “book-list” and the basic data entry ID = “1” along with the extended data (node ID) (step S390).

  The extension data search unit 22 sends the extension data obtained by the search, the basic data storage table name, and the basic data entry ID to the search processing unit 15. Then, the search processing unit 15 sends the basic data storage table name and the basic data entry ID to the basic data search unit 21 and requests the basic data search unit 21 to search for basic data. The basic data search unit 21 searches and acquires basic data corresponding to the acquired extension data from the basic data storage DB 23 (step S400). Specifically, the basic data search unit 21 extracts data rows in which the basic data storage table name and the basic data entry ID match from the basic data storage DB 23, and sends these extracted data rows to the search processing unit 15. .

  The search processing unit 15 sends the search results obtained from the basic data search unit 21 and the extended data search unit 22 to the search result output unit 12, and the search result is output from the search result output unit 12 (step S370).

  In this embodiment, the basic data entry ID and the table ID are separate IDs, but the basic data entry ID may include a table ID. In other words, the table name and basic data may be identified by the basic data entry ID. The basic data identification information described in the claims corresponds to the basic data entry ID and the table ID.

  As described above, according to the first embodiment, the document (XML document) 103 is converted into the basic data storage DB (RDB) 23 and the extended data storage DB (RDB mapping XML-) according to the storage location information table 102 set by the user. DB) 24 is divided and stored, and the storage destination of the stored data is managed, so that desired data can be quickly retrieved with a simple configuration.

  In addition, since basic data that is frequently used is stored in the basic data storage DB 23, basic data that is frequently used is retrieved from the basic data storage DB 23 at a higher speed than when the extended data storage DB 24 is searched for low-frequency use extended data. Can be searched.

  In addition, since the same basic data entry ID as the basic data of the basic data storage table 104 is associated with the extended data of the extended data storage table 105, when searching for basic data from the basic data storage DB 23, Corresponding extension data can be easily retrieved collectively from the extension data storage DB 24. Further, when the extension data is searched from the extension data storage DB 24, the basic data corresponding to the extension data can be easily searched from the basic data storage DB 23. Therefore, the data management apparatus 1 can easily acquire all data originally in the same tree structure as the XML document from the basic data storage DB 23 and the extended data storage DB 24.

  In addition, since the user can designate the XML document by the storage rule condition information 101 so as to divide the XML document into data groups with a predetermined hierarchy at the top and to divide each data group into basic data and extended data, the basic information desired by the user can be specified. Data and extended data can be easily divided. As a result, the XML document can be stored in the basic data storage DB 23 and the extended data storage DB 24 in accordance with a storage rule determined by the user.

Embodiment 2. FIG.
Next, a second embodiment of the present invention will be described with reference to FIGS. In the second embodiment, a new basic data storage table is added to the basic data storage DB 23. In the present embodiment, the same data management apparatus 1 as in the first embodiment shown in FIG. 1 is used.

  Since the basic data storage DB 23 is an RDB, the existing information table (basic data storage table 104) cannot be changed after the database operation is started. On the other hand, another information table different from the existing table can be newly added to the basic data storage DB 23.

  In this embodiment, as an example of a process of adding a new information table to the basic data storage DB 23, a document (document 108 (music) described later) different from the document 103 (book) used in the first embodiment is basically used. A case where data is stored in the data storage DB 23 will be described.

  As an operation procedure of the data management apparatus 1 according to the second embodiment, a process for adding a new document will be described first. Of the additional storage processing of a new document by the data management apparatus 1, description of processing performed by the same processing procedure as the data storage processing of the first embodiment shown in FIG. 2 is omitted.

  When a document (a new document 108 described later) different from the existing document 103 is stored in the basic data storage DB 23, it is necessary to add a new information table to the basic data storage DB 23. When a new information table is added to the basic data storage DB 23, new storage rule condition information (storage rule condition information 106 described later) is input to the data management apparatus 1 from the storage rule input unit 13 in advance. The storage rule input unit 13 stores the new storage rule condition information 106 in the storage rule storage unit 16.

  Here, the new storage rule condition information 106 set in the data management apparatus 1 when adding a new information table will be described. FIG. 9 is a diagram illustrating an example of new storage rule condition information set when a new information table is added. The storage rule condition information 106 shown in FIG. 9 has the same configuration as the storage rule condition information 101 shown in FIG.

  For example, in the conditional expression on the first line of the storage rule condition information 106 shown in FIG. 9, a column named “title” is provided in a table named “music-list”, and this column has a hierarchy in the input document. Indicates that a node value at “/ music / title /” is stored.

  Next, the storage rule determination processing unit 17 instructs the storage destination management unit 19 to generate a database schema according to the storage rule condition information 106. The storage location management unit 19 generates a new storage location information table 107 shown in FIG. 10 based on the storage rule condition information 106 and stores it in the storage location information storage unit 20.

  The configuration of the storage location information table 107 will be described. The storage location information table 107 shown in FIG. 10 has the same configuration as the storage location information table 102 shown in FIG. In the present embodiment, the storage destination information table 107 is created by adding information related to the storage destination of a newly stored document to the existing storage destination information table 102. In the storage location information table 107, for example, the basic data storage table name “music-list”, the column name “music”, and the hierarchical path “/ music / title /” are associated.

  Next, the storage location management unit 19 generates a basic data storage table 109 to be newly added shown in FIG. 11 in the basic data storage DB 23. Note that the storage location management unit 19 corresponds to the basic data storage table creation unit described in the claims.

  FIG. 11 shows the configuration of the basic data storage table 109 whose basic data storage table name is “music-list”. The basic data storage table 109 has the same configuration as the basic data storage table 104 shown in FIG.

  In FIG. 11, the “basic data entry ID” is “1”, the “title” is “fate”, the “title-kana” is “Unmei”, the “artist” is “Beethoven”, and the “artist-kana” is “Beethoven”. The case is shown.

  After a new basic data storage table 109 is generated in the basic data storage DB 23, when a new document 108 to be stored is input to the data input unit 14, this document 108 is sent to the storage execution unit 18.

  Here, the configuration of the document 108 to be newly stored will be described. FIG. 12 is a diagram illustrating an example of a configuration of a document to be newly stored. The document 108 is document data related to music, and has the same configuration as the document 103 shown in FIG. In FIG. 12, the title of the document 103 is “Fate”, the reading of the title is “Unmei”, the author is “Beethoven”, the author's reading is “Beethoven”, the genre is “classic”, and the ranking Is the case of “4 stars”.

  After the document 108 is sent to the storage execution unit 18, the data management apparatus 1 stores the document 108 in the basic data storage DB 23 and the extended data storage DB 24 by the same processing procedure as in the first embodiment. That is, the storage execution unit 18 analyzes the document 108 to extract data of each layer, and inquires the storage rule determination processing unit 17 about the storage location of the extracted data. When there is an inquiry about the data storage destination from the storage execution unit 18, the storage rule determination processing unit 17 causes the storage destination management unit 19 to inquire about the data storage destination.

  The storage location management unit 19 determines whether or not the corresponding storage location information is in the storage location information storage unit 20. If the storage destination information corresponding to the inquired data is in the storage destination information storage unit 20, the storage destination management unit 19 determines that the inquired data is basic data. Then, the storage location management unit 19 extracts the table ID and column ID corresponding to the inquired data from the storage location information table 107. The storage location management unit 19 sends the table ID and the column ID, which are the storage locations of basic data, to the storage execution unit 18 via the storage rule determination processing unit 17.

  When the storage execution unit 18 receives the table ID and the column ID from the storage destination management unit 19, the storage execution unit 18 determines that the data for which the storage destination is inquired is basic data. The storage execution unit 18 stores the basic data of the document 108 in the basic data storage table 109 in the basic data storage DB 23. At this time, the basic data storage DB 23 generates a new basic data row at the time of storage, and assigns a basic data entry ID to the generated data row.

  The storage execution unit 18 stores the basic data entry ID corresponding to the new basic data row and the table ID of the basic data storage table storing the new basic data until the data storage of the document 108 is completed. .

  Thereafter, the storage execution unit 18 determines whether or not all data extracted from the document 108 has been stored in the data management apparatus 1. If the storage execution unit 18 does not store all the data extracted from the document 108 in the data management device 1, the storage destination management unit 19 stores the storage destination information corresponding to the next data in the storage destination information storage unit 20. It is judged whether it is in.

  When the storage destination management unit 19 determines that the storage destination corresponding to the inquired data is not in the storage destination information table 107, the storage execution unit 18 determines that the data for which the storage destination is inquired is extended data. Then, the storage execution unit 18 associates the stored basic data entry ID and table ID with the data for which the storage destination is inquired, and stores it in the extended data storage DB 24 (extended data storage table 110 described later). .

  The data management device 1 performs basic data storage processing in the basic data storage DB 23 and extended data storage processing in the extension data storage DB 24 until all data extracted from the document 108 is stored in the data management device 1. .

  FIG. 13 is a diagram showing the configuration of the newly created extended data storage table. The newly created extended data storage table 110 has the same configuration as the extended data storage table 105 shown in FIG. In this embodiment, the extension data storage table 110 is created by adding extension data to be newly stored to the existing extension data storage table 105.

  For example, the extension data having “node ID” “4” has “parent node ID” “0” and “hierarchical path” “/ music /”. The “node name” is “music”, and the “node value” is none. Further, the “basic data storage table name” is “music-list”, and the “basic data entry ID” is “1”. Note that the data search process of the data management apparatus 1 according to the present embodiment is performed according to the same procedure as that of the data management apparatus 1 of the first embodiment, and thus the description thereof is omitted.

  As described above, according to the second embodiment, the new basic data storage table 109 and the new extended data storage table 110 are generated based on the storage destination information table 102 set by the user. It becomes possible to add a table.

Embodiment 3 FIG.
Next, a third embodiment of the present invention will be described with reference to FIGS. In the third embodiment, a part of a predetermined node (such as the first character of a song title) is extracted, and the extracted information is associated with extension data as additional information.

  FIG. 14 is a diagram illustrating a configuration of a data management apparatus according to the third embodiment. Of the constituent elements in FIG. 14, constituent elements that achieve the same functions as those of the data management apparatus 1 of the first embodiment shown in FIG.

  The data management apparatus 1 according to the present embodiment includes a search request input unit 11, a search result output unit 12, a storage rule input unit 13, a data input unit 14, a search processing unit 15, a storage rule storage unit 16, and a storage rule determination processing unit. 17, the storage execution unit 18, the storage location management unit 19, the storage location information storage unit 20, the basic data search unit 21, the extended data search unit 22, the basic data storage DB 23, and the extended data storage DB 24, as well as extended data additional information storage The unit 31 is provided.

  The extended data additional information storage unit 31 is connected to the storage location management unit 19 and stores additional information (extended data additional information) described later. The storage location management unit 19 according to the present embodiment stores an additional definition information table 112 (described later) generated by the storage rule determination processing unit 17 in the extended data additional information storage unit 31.

  As an operation procedure of the data management apparatus 1 according to the third embodiment, a document storage process will be described first. Of the document storage processing by the data management apparatus 1, description of processing performed by the same processing procedure as the data storage processing of the first embodiment shown in FIG. 2 is omitted.

  Similarly to the first embodiment, storage rule condition information 111 (described later) is input from the storage rule input unit 13 to the data management device 1 in advance. Here, the configuration of the storage rule condition information 111 will be described. FIG. 15 is a diagram illustrating an example of storage rule condition information according to the third embodiment. The storage rule condition information 111 shown in FIG. 15 has the same configuration as the storage rule condition information 101 shown in FIG. The storage rule condition information 111 is information obtained by adding additional definition information (information defining information to be added to extension data) to the storage rule condition information 101.

  The conditional expression (ADDX line) on the fifth line in FIG. 15 is an example of additional definition information (command statement). In the present embodiment, this additional definition information is added to a storage rule when data is stored. The additional definition information is, for example, a command for adding information of a predetermined byte length only to a specific node when storing extension data in the extension data storage DB 24. The information of the predetermined byte length is, for example, a part of another node different from the specific node (a node value having a predetermined byte length).

  In FIG. 15, for the node “/ music / genre /”, an additional definition in the case where the first two bytes of the node value “/ music / title / kana /” is stored in the extended data storage DB 24 as additional information. Information is shown.

  The storage rule condition information 111 having the additional definition information is analyzed by the storage rule determination processing unit 17 and stored in the storage rule storage unit 16. The storage rule determination processing unit 17 generates an additional definition information table that stores additional definition information based on the storage rule condition information 111.

  Here, the configuration of the additional definition information table will be described. FIG. 16 is a diagram illustrating an example of the configuration of the additional definition information table. The additional definition information table 112 is an information table related to additional definition information in which “additional information node”, “byte length”, and “additional information addition destination node” are associated with each other.

  The “additional information node” indicates a node used when creating additional information, and the “additional information addition destination node” indicates a hierarchical path of a node for which additional information is to be created. The “byte length” indicates the size (byte length) of information added to the extended data storage table (extended data storage table 113 described later) as additional information.

  The storage location management unit 19 stores the additional definition information table 112 generated by the storage rule determination processing unit 17 in the extended data additional information storage unit 31. The additional information for 2 bytes is stored in the extended data storage table 113 together with the extended data in the extended data storage table 105 described in the first embodiment.

  Next, the storage rule determination processing unit 17 instructs the storage destination management unit 19 to generate a database schema according to the storage rule condition information 111. Upon receiving a database schema generation instruction from the storage rule determination processing unit 17, the storage location management unit 19 generates a storage location information table 102 based on the storage rule condition information 111 and stores it in the storage location information storage unit 20. Further, the storage location management unit 19 generates a basic data storage table 104 in the basic data storage DB 23.

  After the basic data storage table 104 is generated in the basic data storage DB 23 and the document 103 to be stored is input to the data input unit 14, the document 103 is sent to the storage execution unit 18. The storage execution unit 18 stores the basic data of the document 103 in the basic data storage table 104 in the basic data storage DB 23 by the same processing as in the first and second embodiments.

  Further, the storage execution unit 18 stores the extended data in the extended data storage DB 24 by the same processing as in the first and second embodiments. At this time, in this embodiment, the storage execution unit 18 stores the extended data storage table 113 in the extended data storage DB 24 using the additional definition information table 112 stored in the extended data additional information storage unit 31. The extended data storage table 113 is an information table (node table with additional information) that stores additional information and extended data.

  FIG. 17 is a diagram showing a configuration of an extended data storage table having additional information. The extended data storage table 113 includes “node ID”, “parent node ID”, “hierarchy path”, “node name”, “node value”, “basic data storage table name”, “basic data entry ID”, “additional”. "Information" is associated. In other words, the extended data storage table 113 is an information table in which additional information is associated with the extended data storage table 105 described in the first embodiment.

  In the extended data storage table 113 shown in FIG. 17, the node value “/ music / title / kana /” is added as additional information to the node whose node name is “genre” in the row of “node ID” “5” ( This shows a case where “U” is added for 2 bytes of (title name).

  Here, a configuration example (generation result example) of the basic data storage table and the extended data storage table when a plurality of documents are input from the data input unit 14 will be described. FIG. 18 shows a configuration of the basic data storage table 114 whose basic data storage table name is “music-list”.

  For example, in the basic data with the “basic data entry ID” “2”, “title” is “ripple of the Danube”, “title-kana” is “Danagawa no Sazanami”, and “artist” is “ “Ivanovic” and “artist-kana” are “Ivanovic”.

  FIG. 19 is an extended data storage table corresponding to the basic data storage table shown in FIG. FIG. 19 shows a case where additional information is added to the basic data storage table shown in FIG. 18 based on the additional definition information shown in FIG. As shown in FIG. 19, the extended data storage table 115 corresponding to the basic data storage table 114 includes “node ID”, “parent node ID”, “hierarchy path”, “node name”, “node value”, “basic”. “Data storage table name”, “basic data entry ID”, and “additional information” are associated with each other.

  For example, the extension data having “node ID” “8” has “parent node ID” “7” and “hierarchical path” “/ music / genre /”. The “node name” is “genre”, and the “node value” is “classic”. Further, the “basic data storage table name” is “music-list”, and the “basic data entry ID” is “2”.

  In the extended data storage table 115 illustrated in FIG. 19, a node whose hierarchical path is “/ music / genre /” is, for example, a node in a row whose “node ID” is “8”. The basic data entry ID of this node is “2”. Of the node values included in the basic data with the basic data entry ID “2”, the node value of “/ music / title / kana /” is “Danauga no Sazanami” from the basic data storage table 114 of FIG. is there.

  Therefore, the storage execution unit 18 extracts “Donagawa no Sazanami” as the node value of the node used when creating the additional information. Then, “do” is extracted as information of 2 bytes from “donaugawa no sazanami”, and the extracted “do” is set as additional information. The storage execution unit 18 stores this “do” in the extended data storage table 115 in association with the node in the row whose “node ID” is “8”.

  As described above, in the present embodiment, the user is instructed by the additional definition information to combine the nodes (additional information) of different hierarchies with the nodes of the predetermined hierarchies and store them in the same record. Stores a predetermined node in association with a part or all of the values of other nodes in the same record different from this node. Thereby, it becomes possible to give the node of the combined hierarchy the role of the index of the record which stores the node of the said hierarchy.

  Next, a search process for data stored in the data management apparatus 1 will be described. The description of the same processing as the data search processing of the first embodiment shown in FIG. 8 is omitted. For example, when a search request is made to the extended data storage DB 24 (the extended data storage table 115 to which additional information is added) or the basic data storage DB 23 under a search condition of / music / genre / = “classic”, this search is performed. The request is sent from the search request input unit 11 to the search processing unit 15.

  The search processing unit 15 inquires the storage destination management unit 19 about the hierarchy of / music / genre / in order to obtain a set of data whose hierarchy is “genre” under “music” and whose value is “classic”.

  The storage location management unit 19 extracts from the storage location information table 102 conditions that match the hierarchy inquired from the search processing unit 15, and sends the extracted basic data storage table name and column name to the search processing unit 15. Thereafter, the search processing unit 15 causes the basic data search unit 21 and the extended data search unit 22 to perform basic data search and extended data search.

  In the extended data storage DB 24, the hierarchy of / music / genre / is stored in the extended data storage DB 24, so that the extended data is searched from the extended data storage table 115.

  The extended data search unit 22 can obtain a record indicating a plurality of / music / genre / nodes as a search result. At this time, if the number of records that can be obtained as search results is large, it takes a long time to acquire all the basic data corresponding to the extended data from the basic data storage table 114. In addition, it takes a long time to sort the obtained extended data and basic data, for example, in the order of 50 sounds and provide them to the user.

  Therefore, in the present embodiment, data search processing is performed by adding a predetermined search condition. For example, when a song name starting with line A is required, data search is performed according to the following search conditions. That is, the extended data search unit 22 performs data search according to a search condition of “/ music / genre / =“ classic ”” and “/ music / title / first 2 bytes <“ a ””.

  As a result, the extended data search unit 22 can extract only the music beginning with the line A from the record indicating the node of / music / genre / searched from the extended data storage table 115 in the extended data storage DB 24. .

  The extended data search unit 22 sorts the search results of the extended data in the order of 50 sounds and sends the sorted search results to the search processing unit 15. FIG. 20 is a diagram illustrating an example of a search result after sorting. As shown in the figure, the search result table 116 includes “node ID”, “parent node ID”, “hierarchy path”, “node name”, “node value”, “basic data storage table name”, “basic data entry”. “ID” and “additional information” are associated with each other.

  For example, as a record having “node ID” 11, “parent node ID” = 10, “hierarchy path” = / music / genre /, “node name” = genre, “node value = classic”, “basic data storage table name” "= Music-list", "basic data entry ID" = 7, and "additional information" = a.

  The extended data search unit 22 sends the acquired search results to the search processing unit 15, and the search processing unit 15 sends the search results to the search result output unit 12. Then, the detection result is output from the search result output unit 12. The user may then acquire basic data corresponding to the extended data from the basic data storage table 114 in the basic data storage DB 23 based on the search result.

  In the present embodiment, the case where there is one additional information has been described. However, the number of additional information is not limited to one and may be plural. Further, the additional information is not limited to 2 bytes and may be any size.

  As described above, according to the third embodiment, since additional information is added to the extended data storage table, it is possible to quickly sort the data search results, and to quickly perform the data condition search. become. Further, since additional information is given only to nodes that require a predetermined condition search, the memory size of the extended data storage DB 24 does not need to be increased redundantly.

  As described above, the data management apparatus according to the present invention is suitable for storing XML documents and retrieving data.

It is a figure which shows the structure of the data management apparatus which concerns on Embodiment 1 of this invention. It is a flowchart which shows the storage process procedure of data. It is a figure which shows an example of storage rule condition information. It is a figure which shows an example of a storage location information table. It is a figure which shows an example of a structure of a basic data storage table. It is a figure which shows an example of a structure of the document used as storage object. It is a figure which shows the structure of an extended data storage table. It is a flowchart which shows the search process procedure of data. It is a figure which shows an example of the new storage rule condition information set when adding a new information table. It is a figure which shows an example of the storage location information table newly produced | generated. It is a figure which shows an example of the basic data storage table added newly. It is a figure which shows an example of a structure of the document used as the new storing object. It is a figure which shows the structure of the extension data storage table newly created. FIG. 10 is a diagram illustrating a configuration of a data management device according to a third embodiment. FIG. 10 is a diagram illustrating an example of storage rule condition information according to Embodiment 3. It is a figure which shows an example of a structure of an additional definition information table. It is a figure which shows the structure of the extended data storage table which has additional information. It is a figure which shows the structure of the basic data storage table whose basic data storage table name is "music-list". It is a figure which shows the structure of the extended data storage table corresponding to the basic data storage table shown in FIG. It is a figure which shows an example of the search result after a sort.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Data management apparatus 11 Search request input part 12 Search result output part 13 Storage rule input part 14 Data input part 15 Search processing part 16 Storage rule memory | storage part 17 Storage rule judgment processing part 18 Storage execution part 19 Storage destination management part 20 Storage destination Information storage unit 21 Basic data search unit 21 Search processing unit 22 Extended data search unit 23 Basic data storage DB
24 Extended data storage DB
31 Extended data additional information storage unit 101, 106, 111 Storage rule condition information 102, 107 Storage destination information table 103, 108 Document 104, 109, 114 Basic data storage table 105, 110, 113, 115 Extended data storage table 112 Additional definition Information table 116 Search result table

Claims (6)

In a data management apparatus that divides data included in an XML document and stores the divided data in a relational database or an XML database,
Based on a storage rule relating to a storage location of data to be divided, basic data for storing each data in the XML document in a predetermined data structure set in advance or an extended data in which the data structure of the storage destination is not determined A storage execution unit for storing the basic data in the relational database and storing the extension data in the XML database;
A storage location storage unit that stores, as storage location management information, a location in the relational database in which the basic data is stored and a location in the XML database in which the extended data is stored;
A search processing unit for searching basic data and extended data corresponding to the search request from the relational database and the XML database based on the storage location management information when there is a search request for the data;
A data management device comprising: The relational database stores basic data identification information for identifying the basic data in association with the basic data, and the XML database stores the basic data identification information of the basic data corresponding to the extended data as the extended data. Stored in association with
The data management apparatus according to claim 1, wherein the search unit searches the basic data and the extension data using the basic data identification information.   The search unit, when a storage location of basic data corresponding to the search request is set in the storage location management information, basic data corresponding to the search request from the relational database based on the storage location management information 3. The data according to claim 2, wherein after that, the extended data corresponding to the search request is searched from the XML database based on basic data identification information associated with the searched basic data. Management device.   The search unit searches the XML database based on a storage location of basic data corresponding to the search request when a storage location of basic data corresponding to the search request is not set in the storage location management information. The extended data corresponding to the request is searched, and thereafter the basic data corresponding to the search request is searched from the relational database based on the basic data identification information associated with the searched extended data. Item 4. The data management device according to Item 2 or 3. A basic data storage table creation unit for creating a data table for storing the basic data in the relational database based on the storage rule;
The said storage execution part produces the data table which stores the said extension data in the said XML database based on the said storage rule and the said extension data, The Claim 1 characterized by the above-mentioned. Data management device.   The storage execution unit extracts a part of the extension data based on the addition definition information that defines the information to be added to the extension data, and adds the extracted part of the data to the extension data. The data management apparatus according to claim 1, wherein the data management apparatus is stored in the XML database.

Images