Method for converting relational data into a structured document

• US 6,604,100 B1
• Filed: 02/08/2001
• Issued: 08/05/2003
• Est. Priority Date: 02/09/2000
• Status: Expired due to Term

• Current Assignee: Alto Dynamics, LLC (IP Investments Group LLC)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Tan, Wang-Chiew, Fernandez, Maria F., Suciu, Dan
• Primary Examiner(s): Mizrahi, Diane D.
• Assistant Examiner(s): Wu, Yicun
• Application Number:
  US09/778,749
• Time in Patent Office: 908 Days
• Field of Search: 707/1, 707/2, 707/3, 707/4, 707/10, 707/104.1, 707/513
• US Class Current: 1/1
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/149 Adaptation of the text data for streaming purposes, e.g. Efficient XML Interchange [EXI] format
• CPC Class Codes: G06F 40/151 Transformation
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

A method for converting relational data to XML (Extensible Markup Language) is provided. The method, sometimes referred to as SilkRoute, provides a general, dynamic and efficient tool for viewing and querying relational data in XML. SilkRoute can express mappings of relational data in XML that conforms to arbitrary public document type definitions. Also, SilkRoute can materialize the fragment of an XML view needed by an application and it can fully exploit the query engine of a relational database management system whenever data items in an XML view need to be materialized.

Claims

1. A method for converting relational data from a relational database into a structured document comprising the steps of:

storing a view query that defines a structured document view of the relational database, a structure of the view query being independent of a structure of data in the relational database;

receiving a user query against the structured document view;

forming an executable query by determining a composition of the view query and the user query;

partitioning the executable query into a data extraction portion and a construction portion;

transmitting the data extraction portion to the relational database;

receiving at least one tuple stream from the relational database according to the data extraction portion; and

merging the at least one tuple stream and the construction portion to generate a

structured document, wherein the structured document view is capable of defining a document of arbitrary nesting depth.

2. The method according to claim 1, wherein the user query is in XML-QL.

3. The method according to claim 2, wherein the view query is a RXL query.

4. The method according to claim 3, wherein the executable query is another RXL query.

5. The method device according to claim 1, wherein said step of receiving the user query includes receiving the user query from an application over a distributed network.

6. The method according to claim 5, wherein the distributed network is a private network.

7. The method according to claim 5, wherein the distributed network is the World Wide Web.

8. The method according to claim 5, further including the step of transmitting the structured document to the application over the distributed network.

9. The method according to claim 1, wherein an answer to the executable query includes a fragment of the relational database.

10. The method according to claim 9, wherein the fragment is one data item or a set of data items.

11. The method according to claim 9, wherein the fragment is an aggregate value.

12. The method according to claim 9, wherein the structured document includes the answer to the executable query.

13. The method according to claim 1, wherein the data extraction portion includes at least one SQL query.

14. The method according to claim 13, wherein the construction portion is an XML template.

15. The method according to claim 13, wherein said step of receiving the at least one tuple stream includes receiving one tuple stream for each SQL-query included in the data extraction portion.

16. The method according to claim 1, wherein said step of forming the executable query includes combining fragments of the user query and the view query.

47. The method according to claim 1, wherein a format of the structured document is XML.

17. A computer readable medium including a set of executable instructions stored thereon for converting relational data stored in a relational database into structured document data, the set of instructions including:

forming an executable query from a view query that defines a structured document view of the relational database and a user query, a structure of the view query being independent from a structure of the relational data in the relational database;

partitioning the executable query into a data extraction portion and a construction portion;

retrieving at least one tuple stream from the relational database according to the data extraction portion; and

merging the at least one tuple stream and the construction portion to generate a structured document, wherein

the structured document view is capable of defining a document of arbitrary nesting depth.

18. The computer readable medium according to claim 17, further comprising storage for the view query.

19. The computer readable medium according to claim 18, wherein the view query is a RXL query.

20. The computer readable medium according to claim 19, wherein the executable query is another RXL query.

21. The computer readable medium according to claim 17, wherein an answer to the executable query includes a fragment of the relational database.

22. The computer readable medium according to claim 21, wherein the fragment is one data item or a set of data items.

23. The computer readable medium according to claim 21, wherein the fragment is an aggregate value.

24. The computer readable medium according to claim 21, wherein the structured document includes the answer to the executable query.

25. The computer readable medium according to claim 17, wherein the data extraction portion includes at least one SQL query.

26. The computer readable medium according to claim 25, wherein said step of retrieving the at least one tuple stream includes retrieving one tuple stream for each SQL-query included in the data extraction portion.

27. The computer readable medium according to claim 17, wherein said instruction of forming the executable query includes combining fragments of the user query and the view query.

48. The computer readable medium according to claim 17, wherein a format of the structured document is XML.

28. A computer system for converting relational data in a relational database into structured document data, said system comprising:

a query composer module configured to form an executable query from a view query that defines a structured document view of the relational data and a user query, the view query having a structure that is independent of a structure of the relational data in the relational database;

a translator module coupled to the query composer module configured to receive the executable query, partition the executable query into a data extraction portion and an construction portion, and transmit the data extraction portion to a relational database;

a generator module configured to receive the construction portion from said translator module, receive at least one tuple stream from the relational database based on data extraction portion, and merge the at least one tuple stream and the construction portion to generate a structured document, wherein

the structured document view is capable of defining a document of arbitrary nesting depth.

29. The computer system according to claim 28, wherein said translator module receives a description of a schema of the relational data prior to partitioning the executable query.

30. The computer system according to claim 28, wherein the user query is in XML-QL, the view query is a RXL query and the executable query is another RXL query.

31. The computer system according to claim 28, wherein said query composer module is configured to receive the user query from an application over a distributed network.

32. The computer system according to claim 31, wherein said generator module is configured to transmit the structured document to the application over the distributed network.

33. The computer system according to claim 28, wherein an answer to the executable query includes a fragment of the relational database.

34. The computer system according to claim 33, wherein the fragment is one data item, a set of data items or an aggregate value.

35. The computer system according to claim 33, wherein the structured document includes the answer to the executable query.

36. The computer system according to claim 28, wherein the data extraction portion includes at least one SQL query.

37. The computer system according to claim 36, wherein said generator module receives one tuple stream for each SQL-query included in the data extraction portion.

38. The computer system according to claim 28, wherein said query composer module combines fragments of the user query and the view query to form the executable query.

39. The computer system according to claim 28, wherein the data extraction portion is executable by the relational database.

40. The computer system according to claim 28, where in the query composer module includes

a pattern matcher module configured to match patterns of the user query and the view query to obtain a solutions relation, in which each tuple represents a match; and

a rewriter module configured to rewrite each tuple.

49. The computer system according to claim 28, wherein a format of the structured document generated by the generator module is XML.

41. A method of forming a composed query for use in converting relational data of a relational database into XML data, said method comprising the steps of:

receiving a user query in an XML based language requesting relational data;

forming a view query in a transformation language, the view query defining a structured document view of the relational data and having a structure that is independent from a structure of the relational data of the relational database; and

composing an executable query in the transformation language from the view query and the user query, wherein

the structured document view is capable of defining a document of arbitrary nesting depth.

42. The method according to claim 41, wherein the transformation language is RXL.

43. The method according to claim 41, wherein said step of composing includes the steps of:

matching patterns of the user query and the view query to obtain a solutions relation, in which each tuple represents a match; and

rewriting each tuple into a clause in the transformation language.

44. The method according to claim 43, wherein said step, of matching patterns includes the steps of:

constructing a view tree from the view query; and

evaluating the user query on the view tree.

45. The method according to claim 43, wherein said step of rewriting includes the step of constructing at least one block using from and where clause of the view query and a construct clause of the user query.

46. The method according to claim 43, wherein said step of rewriting each tuple into a clause in the transformation language is conducted on the basis of from/where clauses of the view query, the solutions relation, and construct clauses of the user query.