KR20150074611A - Relational Database, Translating Method and Apparatus From data to XML - Google Patents

Abstract

The present invention relates to a relational database for storing an eXtensible markup language (XML) in a relational database in a more effective structure and dynamically restoring the same, and to a method and a device for converting data to an XML. The method according to an embodiment of the present invention is a method for restoring an XML from data stored in a relational database (RDB). The method comprises the steps of: (a) converting data stored in the RDB into an entity; and (b) converting the converted entity to an XML. A data storing table of the RDB may convert data, which include a conversion reference column including at least one phrase dynamically changed during an XML conversion process in Step (b), into an XML.

Description

[0001] Relational database, method and apparatus for converting data to XML [0002]

The present invention relates to a relational database, and a method and apparatus for converting data to XML. More particularly, the present invention relates to a relational database capable of storing an XML, eXtensible Markup Language (XML) into a relational database in a more efficient structure and dynamically restoring it, and a method and apparatus for converting data into XML will be.

In the early days, data was simply stored and read using the file system provided by the operating system. In order to manage or access such data more efficiently, the application programmer had to develop the necessary application programs directly in the file system. At that time, we had to constantly change or even redevelop the application each time the user's needs changed, and the functionality was also extremely limited at the same time for many users.

For the first time in the early 1960s, the term "database" was defined as "a collection of operational data that was integrated and stored for the application systems of an organization to be shared" DBMS (Database Management System), a system for managing databases, has been introduced. Since then, DBMSs such as IMS and Total based on hierarchical data model and network data model have been developed and showed excellent performance in a business area having a hierarchical structure such as sales network information and department organization information. However, these DBMSs have a decisive disadvantage, because changes to the database have a significant impact on the performance of the application, since the data is pointers and applications have been developed to take full advantage of those pointers. Moreover, maintaining consistency in such databases was not difficult.

To solve these problems, there is a relational database (RDBMS).

A method for storing and converting an XML (Extensible Markup Language) to an existing relational database is as follows. The entire XML document is simply stored as a string, or the content of each node is inserted into each item of the relational DB : 1, and then converted to XML.

The existing storage and conversion method has a problem that the content of each XML tag is stored in the relational database as it is structured and stored, resulting in waste of space and too many database table records. .

In addition, even when the contents of the XML structure can be changed dynamically, it is impossible to dynamically change the contents of the XML structure according to the logic without changing the parent-child relationship of the relational database.

Korean Patent Publication No. 2006-0081255

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a method and apparatus for storing data in a relational database including a logic in a table in which data is stored, To provide a relational database.

It is another object of the present invention to provide a method and apparatus for storing dynamic content, including logic,

More particularly, the present invention relates to a method and apparatus for storing data stored in a column that can store data in which a dynamic change of data may exist, including logic, separately, so as to convert data stored in a relational database into XML And to provide a method and apparatus for converting to XML.

According to another aspect of the present invention, there is provided a method and an apparatus for converting data, which can be dynamically changed, into XML into XML according to user operation information input through a user interface (UI).

The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems which are not mentioned can be clearly understood by those skilled in the art from the following description.

According to a first aspect of the present invention, a relational database according to the present invention is a relational database for inputting or storing data that can be restored in an extensible markup language (XML) A table storing decompressed data in a language, the table including a transformation reference column containing at least one syntax that is dynamically changed in the XML transformation process.

The relational database may predefine and store terms available for inputting or storing the data that can be dynamically changed, and may store data corresponding to the predefined term.

The at least one syntax may include logic.

The data that can be dynamically changed include: And the logic is data including the logic.

The data including the logic may be data including at least one of a conditional statement, a loop statement, and a variable value process.

At least one of the condition inquiry condition, the repeating condition of the loop, and the setting of the variable value of the variable value process may be determined using the user's operation information input through a user interface (UI).

The transformation reference column may exist in a table of a node master.

The transformation reference column may exist for each table of the individual nodes.

The transformation reference column may exist for each table of the node master and each table of the individual nodes.

According to an aspect of the present invention, there is provided a method of converting data into XML according to a second aspect of the present invention, comprising: converting data stored in a relational database into an extensible markup language (XML) (A) converting data stored in the relational database into an object; And (b) converting the transformed object to XML, wherein the data storage table of the relational database includes a transformation reference column including at least one syntax that is dynamically changed during the XML transformation process in the step (b) . ≪ / RTI > Wherein the step (b) comprises: transforming the data included in the transformed reference column into XML; converting the at least one syntax contained in the transformed reference column into XML into a document composed of the transformed XML at the step (b) Information.

According to an embodiment of the present invention, the relational database stores predefined terms and data corresponding to the predefined terms, and information obtained by converting the data included in the conversion reference column into XML is stored in the conversion reference column If at least one of the inputted or stored at least one sentence corresponds to the predefined term, the data included in the converted reference column is converted into XML using data corresponding to the corresponding predefined term .

According to an embodiment, the step (b) may further comprise the step of: using data corresponding to the corresponding predefined term and a parent-child node relationship of the transformed objects, Data can be converted to XML.

According to an embodiment, when the logic includes the logic, the step (b) includes the steps of: analyzing the logic based on data corresponding to the predefined term, Data can be converted to XML.

If the logic of the at least one statement is included, the step (b) may convert the syntax included in the conversion reference column into XML by interpreting the logic.

Wherein at least one of the at least one statement includes at least any one of a condition statement, an iterative statement, and a variable value process, and at least one of the conditions of the condition statement, the repeated exit condition of the loop statement, Wherein the step (b) comprises the steps of: analyzing the logic using the operation information of the user to determine a syntax included in the conversion reference column, It can be converted to XML.

The at least one syntax is: And the logic may be included.

The logic may be at least one of a conditional statement and a loop statement.

The step (b) may convert a child node of the parent node to the XML before converting the parent node of the transformed object into XML.

In the step (b), XML transformation may be started from a leaf node of the transformed object, and the XML may be sequentially transformed to a root node.

The method of converting the syntax included in the transformation reference column into XML may further comprise the step of (c) determining a node object to be converted into XML from the data converted into the object, wherein (b) Only node objects determined in step c) can be converted to XML.

In the step (b), the XML transformation is started from the child node of the lowest node among the node objects determined in the step (c), and sequentially converted to XML from the parent node of the node object determined in the step (c) have.

According to an aspect of the present invention, there is provided an apparatus for converting data into XML according to a third aspect of the present invention, comprising: an object conversion unit for converting data stored in a relational database into an object; And an XML transformation unit for transforming the transformed object into XML. The data storage table of the relational database may include a transformation reference column including at least one syntax that is dynamically changed in the XML transformation process.

The present invention can reduce the space consumption of the relational database and reduce the number of the database table records because the XML contents can be converted into logic and stored instead of storing the contents as they are.

In addition, the present invention can dynamically convert XML contents. That is, the present invention can easily and dynamically convert XML contents according to logic such as conditional statements, loop statements, or variable value processing.

The effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood to those of ordinary skill in the art from the following description.

1 is a diagram showing an example of a table in which data of an existing relational database is stored.
2A is a diagram showing an example of a form in which data of a relational database is stored with a relational structure.
FIG. 2B is a diagram illustrating an example of a relationship structure of parent-child relationship types of data stored in a relational database.
3 is a diagram showing an example of a table format of a relational database according to an embodiment of the present invention.
4 to 6 are views for explaining an example of a process of storing contents of a screen (XML structure) in a relational database according to an embodiment of the present invention with a relational structure.
Figures 7 and 8 are diagrams showing examples of nodes where a transformed reference column is present.
9 is a block diagram of an apparatus for converting data into XML according to an embodiment of the present invention.
10 is a flowchart illustrating a method of converting data into XML according to an embodiment of the present invention.
FIG. 11 is a flowchart showing an example of a concrete process of the XML conversion unit converting an object into XML.
FIG. 12 is a diagram illustrating an exemplary configuration of an apparatus for converting data into XML according to another embodiment of the present invention. Referring to FIG.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

In this specification, a singular form may include plural forms unless specifically stated in the phrase. It is noted that the terms "comprises" and / or "comprising" used in the specification are intended to be inclusive in a manner similar to the components, steps, operations, and / Or additions.

Extensible Markup Language (XML) is designed to describe content that is not intended for display, and allows the user to define new tags to describe the structure. XML has the advantage of providing various characteristics according to data structure such as data structure reuse, flexibility of output format, search function of data structure, and so on, since data structure, contents, and output format are defined as whole data. The basic unit in XML is an Element, which allows the user to freely define the element. You can have text, an element, or a mixture of text and elements inside an element. Such XML has become a standard for information representation and electronic data exchange on the Internet due to the flexibility of the information expression of the language itself.

XML can be stored in a relational database for reasons such as ease of management, and can restore XML from data stored in a relational database.

A relational database (RDB) is a collection of data items consisting of a set of formalized tables, which are sets of related tables. Relational databases are relatively easy to create and use, but most of all have the advantage of being easy to extend. After creating the database for the first time, you can add new data items to the database without changing related applications. The design of the database is called the Entity Relationship (ER) model. Depending on the ER model, a database is created. A database consists of one or more tables and tables can be created based on entities in the ER model.

1 is a diagram showing an example of a table in which data of an existing relational database is stored.

In order to facilitate the understanding and explanation of the present invention, for example, terms of components of existing relational database tables will be described with reference to FIG.

A table is a basic data storage structure of a relational database, and a table can be composed of a plurality of rows. That is, in FIG. 1, the entire table of employee information is a table.

A table can be represented by a two-dimensional structure of a column and a row.

Row is another type of data that constitutes one table. In Fig. 1, {1} Kim Cheol-soo 300 60} can be a single column, {2} have.

If the row represents data in the horizontal direction, the column may mean data in the vertical direction.

A column is a component that constitutes a row in the vertical direction. Taking FIG. 1 as an example, {column name: Kim Cheol-soo Ebagdhdong Hong Gil-dong Lim Jung Jung Yi Soon Shin} can be a column, and {column manager's deputy manager's deputy director} can be another column.

One space where columns and rows overlap is called a field.

2A is a diagram showing an example of a form in which data of a relational database is stored with a relational structure.

Referring to FIG. 2A, a primary key and a foreign key will be described.

One or more columns that can specify each row in one sense are called primary keys. 2A, for example, {player number} in the employee information table 1, {department number} in the department information table 2, and {area code} in the local information table 3 can be the basic keys.

A foreign key is a column that is used as a primary key of another table and is used to connect the relationship with the table. 2A, for example, {department number} connecting the employee information table 1 and the department information table 2 can be a foreign key. In Fig. 2A, {area code} connecting the department information table 2 and the local information table 3 can be a foreign key.

That is, the data of the relational database can be stored with a relational structure through a foreign key or the like.

FIG. 2B is a diagram illustrating an example of a relationship structure of parent-child relationship types of data stored in a relational database.

Specifically, FIG. 2B illustrates an example of a parent-child relationship structure that can be formed in the case of the data of FIG. 2A.

2B, when the employee information node 20 is a parent of the employee number node 21, the employee name node 22, the rank node 23, the salary node 24, and the department information node 25, Node. In addition, the employee information node 20 may be a root node which is the highest parent node having no parent node.

The employee number node 21, the employee name node 22, the rank node 23, the salary node 24 and the department information node 25 are child nodes of the employee information node 20, It may be a parent node of a child node of each node.

For example, a department name node 25_1 and a region code node 25_2 may exist as child nodes of the department information node 25. That is, the department information node 25 may be the parent node of the department name node 25_1 and the region code node 25_2.

The department name node 25_1 and the area code node 25_2 may also be parent nodes. For example, in FIG. 2B, the area code node 25_2 may be a parent node of the area name node 25_2_1, and the area name node 25_2_1 may be a child node of the area code node 25_2.

3 is a diagram showing an example of a table format of a relational database according to an embodiment of the present invention.

Referring to FIG. 3, a table format of a relational database according to an embodiment of the present invention includes a column (Colum) called a transform reference column 10 in a table of an existing relational database.

The conversion reference column 10 may not only be represented by a column (Colum) as shown in FIG. 3, but may also be represented by a row, depending on the type of the table. That is, the conversion reference column 10 is a name for facilitating understanding of the invention, and may also include the meaning of a space formed by a row.

The transformation reference column 10 may include a syntax that includes at least one syntax that changes dynamically during the XML transformation process. And may be information input to the conversion reference column 10 or information input by a user to be stored.

The at least one syntax that is input or stored in the transformation reference column 10 may be logic-included data.

Specifically, the data including the logic may be data including at least any one of conditional statements, loop statements, and variable value processing.

More specifically, an example of a conditional statement may be an if-statement specifying a condition, an if-else statement, or a switch-case statement shifting to a desired result according to a condition.

There are various types of iterations such as a for statement that is a repetition by numerical value, a while statement which is a conditional iteration, and a loop statement.

The variable value processing may include outputting the output value designated by the determined variable value when the variable value is determined according to the input information.

The input information that can be used to determine the variable value may be the information that the user has manipulated the UI through the user interface (UI) or the input information.

For example, variable values can be determined differently depending on the position selected in the UI window, the selected button, and the like, and can be processed with different output values.

As in the case of variable value processing, even in the case of conditional statements and loop statements, the user can perform logical processing of conditional statements or loop statements using information manipulated by the user through the UI or inputted information.

That is, the condition of the condition statement or the numerical value or condition of the loop statement can be set and changed based on the information manipulated by the user or the information inputted.

3, a specific example of the transformed reference column 10 will be described. In the transformed reference column 10, a row having an ID N3, a Tag ID T3, and a Parent ID N1, Field may include data such as the following as an example of data including logic capable of dynamically changing.

#if (Condition A)

 <SubNodeA />

#end

#if (condition B)

 <SubNodeB />

#end

If the condition is A, the data is converted into XML and outputted. If the condition is B, the data is converted to XML and outputted. If the condition satisfies both A and B, the data is converted into XML It means to convert and output SubNodeA and SubNodeB.

SubNode A and SubNode B may be preset or nodes stored in a relational database according to the present invention.

The condition may be determined by user UI manipulation or input.

Subsequently, in FIG. 3, when the contents of the table of the Node 30 are converted into XML, an XML document such as 31 in FIG. 3 can be obtained.

Referring to the XML document as 31 in FIG. 3, if the condition is A, the SubNodeA is converted into XML and outputted. If the condition is B, the SubNodeB is converted into XML and outputted. If the condition satisfies both A and B, To convert SubNodeA and SubNodeB to output. That is, the same contents as those stored using the logic in the transformation reference column 10 in the relational database according to an embodiment of the present invention.

In the case of an existing relational database, the contents of the XML document must be all entered and stored in the table.

Thus, the relational database according to an embodiment of the present invention in which the transformed reference column 10 exists in comparison with the existing relational database can be reduced in space where the same contents are autonomous.

As described above, the conversion reference column 10 is not limited to a column (Colum) as shown in FIG. 3, and may be represented by a row according to the type of the table. In other words, when the roles of a row and a column are changed in the table described with reference to FIG. 1 and FIG. 2A, the transformed reference column 10 may appear as a row.

Referring to Figures 4-8, more specifically, the relational database and transform reference column 10 according to an embodiment of the present invention will be described.

4 to 6 are views for explaining an example of a process of storing contents of a screen (XML structure) in a relational database according to an embodiment of the present invention with a relational structure.

Referring to FIG. 4, a component (41) composed of XML named ComA is arranged in the A subordinate. A screen in which A, B, C, and D are respectively arranged in FIG. 4 may be a preset form (40).

Referring to FIG. 5, the XML structure of FIG. 4 is changed to a Parent-Child form.

5, the R: Form is a root node, and the ComA 41 is a child node of A, which is a child node of A, (41). &Lt; / RTI &gt;

Referring to FIG. 6, an example in which the contents of the relationship structure of FIG. 5 is stored in a relational database in the form of a table can be seen.

In FIG. 6, a node master 61 is a master table storing basic information of an XML tag. That is, the node master 61 may be a data structure technique for minimizing redundant data by collectively storing the basic information of the XML tag in one place.

For example, in the node master 61, the tag ID value T1 stores information about the XML tag in the form <Form>. In other nodes, if the ID value is T1, the entire contents of the <Form> tag are not stored You do not have to worry about data redundancy.

Referring to FIG. 6, the node master 61 stores Form, Div, and ComA, which are tags in FIG. 5, as Tag IDs T1, T2, and T3, respectively. In addition, the node master 61 can input the logic syntax into the transformation reference column 10 when the transformation reference column 10 exists and the administrator needs to change the data dynamically for various reasons such as UI operation of the user.

That is, the contents of the transformation reference column 10 may be input by a relational database or an administrator of the XML, or the content may be determined using a separate file stored in the memory. A rule or a definition of what file is a separate file stored in the memory can be preset.

That is, an administrator can input a logic statement using an if statement, which is a conditional statement as shown in FIG. 6, in the conversion reference column 10.

#if (Condition A)

 <SubNodeA />

#end

#if (condition B)

 <SubNodeB />

#end

That is, the administrator can input data in which the output value can be changed dynamically according to logic using conditional statements, loop statements, and / or variable value processing in the conversion reference column 10 when dynamic change of data is required.

By allowing the administrator to enter data that can dynamically change output values according to logic in the transformation reference column (10), it is possible to change the contents according to logic without changing the parent-child relationship of the database, unlike existing relational databases. have. In addition, the administrator can flexibly utilize the transformation reference column (10) in various forms, such as changing the relationship structure according to logic, storing it as a string, adding a node character, or storing a child node only as a string.

7 and 8 are diagrams showing examples of nodes in which the transformed reference column 10 is present.

Referring to FIG. 7, the transform reference column 10 may be included in each of the individual nodes. If the transformed reference column 10 is included in each of the individual nodes, the contents of the transformed reference column 10 can be modified for each individual node.

Specifically, initially, the contents of the transformation reference column 10 of the node master 61 are copied to each of the individual nodes, and after the copying, the transformation reference column 10 existing in each node for each individual node can be managed have.

More specifically, for example, the time at which the contents of the transformation reference column 10 of the node master 61 is copied to each of the individual nodes may be copied when the components are placed in a template.

Referring to FIG. 8, unlike FIG. 7, the transformed reference column 10 is held by the node master 61 and only the contents of the transformed reference column 10 can be collectively modified based on the tag name. That is, when the transformed reference column 10 exists only in the node master 61 as shown in FIG. 8, the transformed reference column 10 corresponding to the contents changed when the contents of the transformed reference column 10 is changed on the basis of the Tag ID of the node master 61 And can be applied collectively to each node.

9 is a block diagram of an apparatus for converting data into XML according to an embodiment of the present invention.

Referring to FIG. 9, an apparatus 100 for converting data into XML according to an embodiment of the present invention may include an object conversion unit 110 and an XML conversion unit 130, As shown in FIG.

The object conversion unit 110 may convert the data stored in the relational database 200 into an object.

The relational database 200 may include a transformation reference column 10 in a relational database 200 according to one embodiment of the present invention.

The XML conversion unit 130 may convert the converted object into XML.

More specifically, the XML conversion unit 130 converts the syntax included in the conversion reference column 10 into XML, and the document composed of the XML converted by the XML conversion unit 130, And may include information obtained by converting a syntax into the XML.

More specifically, the relational database 200 according to the present invention may store data corresponding to predefined terms and predefined terms.

If there is a predefined term among at least one phrase that can be input or stored in the conversion reference column 10 by a user, an administrator, or the like, the XML conversion unit 130 converts the pre- The syntax contained in the transformation reference column 10 can be converted into XML using data corresponding to the defined term.

The predefined terms stored in the relational database 200 and the data corresponding to the predefined terms may be stored in the relational database 200 or in a separate storage device connected to the relational database 200. [

In addition, if there is a predefined term in the data input to the transformation reference column 10, the XML transformation unit 130 transforms the data corresponding to the term corresponding to the predefined term, Using the parent-child node relation, the syntax contained in the transformation reference column (10) can be converted into XML.

For example, '$ childnode' can be defined as a predefined term representing all child nodes of a particular node, and data corresponding to predefined terms and corresponding predefined terms can be stored.

The data corresponding to the predefined term may be data using a parent-child relationship between the nodes stored in the relational database 200. For example, if the predefined term is '$ childnode', the data corresponding to '$ childnode' may be data related to the identifier of a child node of a particular node using a parent-child relationship between the nodes.

Data corresponding to predefined terms and predefined terms can be set by the administrator.

If the transformed reference column 10 includes logic such as conditional statements, looped statements, and / or variable value processing, the XML transformation unit 130 may analyze the logic and convert the logic included in the transformed reference column 10 You can convert the syntax to XML. Logic consisting of conditional statements, loop statements, and / or variable value processing, etc., can be stored in the relational database 200 with the data needed to interpret the predefined terms and logic representing the logic.

The XML conversion unit 130 determines conditions or numerical values according to the user's operation information or input information input through the UI of the user interface providing apparatus 300 in the process of analyzing the logic inputted or stored in the conversion reference column 10 To interpret the logic.

The XML conversion unit 130 may convert the parent node's child node to XML before converting the parent node to XML.

That is, the XML transformation unit 130 may start XML transformation from a leaf node and sequentially perform XML transformation from the bottom node to the root node.

 The object determining unit 120 may determine an object to be converted into XML among the objects converted by the object converting unit 110. [ That is, when converting only some objects, not all objects, to XML according to the necessity of an administrator, a user's input, etc., the object determining unit 120 determines an object to be converted into XML by using an administrator's need or a user's input .

When the object determining unit 120 determines an object to be converted into XML, the XML converting unit 130 can convert only the objects determined by the object determining unit 120 into XML, and the object determining unit 120 determines Only the contents of the transformation reference column (10) contained in the objects can be subjected to logic analysis and transformed into XML.

The XML transformation unit 130 starts the analysis for the XML transformation from the child node at the bottom of the objects determined by the object determination unit 120, and then, at the bottom of the object determined by the object determination unit 120, XML conversion can be performed sequentially from top to bottom.

10 is a flowchart illustrating a method of converting data into XML according to an embodiment of the present invention.

Referring to FIG. 10, a method of converting data into XML according to an embodiment of the present invention will be described. The object transformation unit 110 transforms data stored in the relational database 200 according to an embodiment of the present invention into an object (Step S1010).

The object determining unit 120 may determine a node object to be converted into XML (step S1020).

The XML conversion unit 130 may convert the node object determined by the object determination unit 120 into XML (step S1030).

The XML converted by the XML conversion unit 130 may be output (step S1040).

11 is a flowchart illustrating an example of a concrete process of the XML conversion unit 130 converting an object into XML.

Referring to FIG. 11, the XML transformation unit 130 may extract a child node list from a node object to be transformed (step S1031).

The XML conversion unit 130 can perform XML conversion on the child node (step S1032).

Specifically, the XML transformation unit 130 performs XML transformation from a child node existing at the bottom of the child nodes, performs XML transformation of the parent node of the bottom node, and then performs XML transformation on the parent node of the parent node of the bottom node By doing so, you can perform XML conversions sequentially from bottom to top.

Since the XML transformation unit 130 performs XML transformation in the direction from the child node to the parent node, the XML transformation must be performed also in each child node, and the step S1032 may be recursively called and processed .

The reason why the XML transformation unit 130 performs the XML transformation in the direction from the child node to the parent node is that there may exist a case where the logic is analyzed using the information of the child node in the parent node. For this reason, the XML transformation unit 130 can perform the XML transformation in the direction from the child node to the parent node, thereby improving the speed of the XML transformation and reducing errors in the XML transformation.

In addition, since the present invention can have data including logic by the transform reference column 10 and information of the child node may be needed for logic analysis, the XML transform unit 130 transforms the data from the child node to the parent node You can do XML conversion in the direction of

The XML conversion unit 130 may add all the nodes present in the child node list to XML (step S1033), add the start tag XML and convert the data of the transformation reference column 10 to XML (S1034 step).

The XML conversion unit 130 interprets the logic included in the data of the conversion reference column 10 and converts the logic into XML. For example, the document converted from the logic using the if statement included in the conversion reference column 10 in FIG. 3 by the XML conversion unit 130 may be the same as 31 in FIG.

The XML conversion unit 130 may convert the content included in the transformation reference column 10 into XML, add the child node to the XML-converted content and add the end tag XML (steps S1035 and S1036) .

The relational database 200 according to an embodiment of the present invention can reduce the consumption of space of the relational database 200 because the XML contents can be converted into logic and stored instead of storing the contents as they are, The number of records can be reduced.

In addition, an apparatus and method for converting data to XML according to an embodiment of the present invention can dynamically convert XML contents. That is, an apparatus and method for converting data to XML according to an embodiment of the present invention can easily and dynamically convert XML contents according to logic such as conditional statements, loop statements, or variable value processing.

FIG. 12 is a diagram illustrating an exemplary configuration of an apparatus for converting data into XML according to another embodiment of the present invention. Referring to FIG.

Referring to FIG. 12, an apparatus 100 for converting data into XML according to an embodiment of the present invention includes a system bus 101, a CPU 102, a memory 103, a storage 104, And a network interface 105 for communication with the client device. The computer program code embodying the method of converting data of the above-described embodiment of the present invention into XML may be stored in the storage 105 and loaded into the memory 103 and executed by the CPU 102. [ The component may be software or hardware such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, the components are not limited to software or hardware, and may be configured to be in an addressable storage medium and configured to execute one or more processors. The functions provided in the components may be implemented by a more detailed component or may be implemented by a single component that performs a specific function by combining a plurality of components.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

Claims (14)

1. A method for restoring data stored in a relational database (RDB) into an extensible markup language (XML)
(A) converting data stored in the relational database into an object; And
And (b) converting the transformed object into XML,
Wherein the data storage table of the relational database includes a transformation reference column including at least one statement that is dynamically changed in the XML transformation step in the step (b). The method according to claim 1,
Wherein the step (b) includes converting the at least one syntax contained in the conversion reference column into XML, and converting the XML into XML. The method according to claim 1,
The step (b)
And transforming the at least one statement contained in the transformed reference column into XML using the node relation of the transformed objects. The method according to claim 1,
Wherein the at least one syntax comprises:
A statement including at least one of a conditional statement, a loop statement, and a variable value processing,
At least one of the condition inquiry condition, the repeating exit condition of the loop statement, and the setting of the variable value of the variable value process is determined using the user's operation information input through a user interface (UI)
The step (b)
And translating the data into XML by parsing the logic using the user's operational information and converting at least one statement contained in the translation reference column to XML. The method according to claim 1,
The step (b)
And transforming the data from the child node of the parent node to the XML before converting the parent node of the transformed object into XML. The method according to claim 1,
The step (b)
Starting from a leaf node of the transformed object, and sequentially converting the transformed XML to a root node. The method according to claim 1,
The method of converting the data into XML includes:
(C) determining a node object to be converted into XML from the data converted into the object,
The step (b) may convert only the node object determined in the step (c) into XML. 8. The method of claim 7,
The step (b) may include: starting XML transformation from a child node of the lowest node among the node objects determined in the step (c), and sequentially converting the XML object to a parent node of the node object determined in the step (c) How to convert data to XML. An object conversion unit for converting the data stored in the relational database into an object; And
And an XML conversion unit for converting the converted object into XML,
Wherein the data storage table of the relational database comprises a transformation reference column that includes at least one statement that is dynamically changed during the XML transformation process. 10. The method of claim 9,
Wherein the XML conversion unit includes information obtained by converting the one or more statements included in the conversion reference column into the XML into a document composed of XML converted by the XML conversion unit. 10. The method of claim 9,
The step (b)
And transforming the data included in the transformed reference column into XML using the node relation of the transformed objects. 10. The method of claim 9,
Wherein the at least one syntax comprises:
A statement including at least one of a conditional statement, a loop statement, and a variable value processing,
At least one of the condition inquiry condition, the repeating exit condition of the loop statement, and the setting of the variable value of the variable value process is determined using the user's operation information input through a user interface (UI)
Wherein the XML conversion unit comprises:
And translating the data into XML by analyzing the logic using the operation information of the user and converting at least one syntax contained in the conversion reference column into XML. 1. A relational database for inputting or storing restorable data in an extensible markup language (XML)
A table for storing recoverable data in an expandable markup language,
Wherein the table comprises a transformation reference column containing at least one syntax that is dynamically changed in the XML transformation process. 14. The method of claim 13,
Wherein the at least one statement comprises logic.

Images