Method of storing extensible markup language file and inserting relational database sheet

Abstract

The expandable markup language file storing method includes the following steps: saving the dependency relationship between modes in the relationship database system list; creating one mapping file for each of the name spaces of the expandable markup language file; creating one relationship database list for each complicated type element, global element and repeatedly appeared simple type element in the mapping file; and inserting the element value and attribute value of the expandable markup language file into the corresponding database list. The method of inserting the element value of the expandable markup language file into the relationship database list includes the steps of: obtaining the mode of the expandable markup language file, reading the database mapping file of the expandable markup language file, and traveling the expandable markup language file to insert the element value into corresponding relationship database list. The present invention has small storing space occupied and efficient inquiry.

Description

technical field [0001] The invention relates to the field of extensible markup language, in particular to a method for storing extensible markup language files and inserting relational database tables. Background technique [0002] With the rapid development of the Internet, xml (Extensible Markup Language, Extensible Markup Language), as a new standard for data representation on the Internet, is being widely used due to its advantages of self-description, flexibility, scalability and platform independence. It is used in various web applications. [0003] How to store xml files so as to effectively manage their data has become a hot research topic today. In recent years, a lot of research work is dedicated to applying database technology to the storage of xml files, using the mature technology of database to store xml files. The current mainstream form of xml database is to use relational databases to store xml files, such as Oracle9i, SQL Server 2000 and other relational ...

AI Technical Summary

Problems solved by technology

The two methods have their own advantages and disadvantages. Using the former method, the XML Schema is mapped to multiple interrelated tables in the database to store the XML files and then querying them will result in multi-table joins, making the query efficiency very low, and in When reorganizing the xml hierarchy, it is not only inefficient but also difficult to restore the original, and there is no good "round trip" (the consistency of the stored xml document and the returned xml document)

Using the latter method to store the xml file, because a large number of tags are used in the xml file, a large number of tags will take up a lot of storage space, so adopting this method will waste a lot of storage space, according to statistics, the average is about 40%. Although the method saves the data content and hierarchical structure of the xml file, the SQL query cannot go deep into the fields of the file. The only way to query the file part is to return the entire file and query after parsing. It is not suitable for large files or multi-file queries. Happening

Images