System and method of translating a universal query language to SQL

• US 20020078041A1
• Filed: 10/12/2001
• Published: 06/20/2002
• Est. Priority Date: 10/13/2000
• Status: Abandoned Application

• Current Assignee: Cytaq, Inc.
• Original Assignee: Cytaq, Inc.
• Inventors: Wu, William Chyi
• Application Number:
  US09/976,439
• Publication Number:
  US 20020078041A1
• Time in Patent Office: Days
• US Class Current: 707/4
• CPC Class Codes: G06F 16/2452 Query translation
• CPC Class Codes: G06F 16/86 Mapping to a database

Abstract

A system and method for translating a universal query language UQL into a relational query language such as SQL. The method first determines whether there are any UQL rule properties. If so, the rule is substituted for the rule property. Next, for each resource and resource property, a relational table is assigned and given an ID. Assigned tables are placed into a table list. Following this step, for each resource property, implied conditions are generated and placed into a condition list and, if needed, additional tables are generated and assigned ids. Then, for each UQL primitive property, a table and column is identified according to a table.column format and placed into a column list. Finally, any predicates are resolved into explicit conditions and the conditions are placed into the condition list. From the column list, the table list and the condition list an SQL statement is formed for querying the relational database.

Claims

1. A method of translating a query based on a resource-property model into a statement for querying a relational database, comprising:

for each rule property in or derived from the resource-property query,

substituting the rule string for the rule property;

for each resource and resource property in or derived from the query,

assigning a relational table having an id to the resource or resource property and entering the assigned table id into a table list;

for each resource property in or derived from the query,

determining any implied conditions based on the resource property and entering the implied conditions into a condition list;

for each primitive property in or derived from the query,

assigning a table and column to the primitive property and entering the table and column into a column list;

for each predicate in or derived from the query,

resolving the predicate into one or more conditions and entering the one or more conditions into the condition list; and

forming an a relational query statement from the column list, the table list and the condition list.

2. A system for translating a query language, comprising:

a query translator;

a first input coupled to said translator for receiving a universal query language statement;

a second input coupled to said translator for receiving a configuration information; and

an output coupled to said translator for generating a structured query language statement.

3. A system for translating a query language as recited in claim 2, wherein said configuration information provides a property mapping information between resources in the universal query language statement and the structured query language statement.

4. A system for translating a query language as recited in claim 3, wherein said translator includes a table for translating to said structured query language.

5. A system for translating a query language as recited in claim 2, wherein said configuration information further comprising:

a first entity including an identification field and an identity field of a said first entity;

a second entity including an identification field and an identity field of said second entity; and

a third entity having a first field for identifying an entry in said first entity to link the first entity and said third entity together.

6. A system for translating a query language as recited in claim 5, wherein said third entity further including a second field for identifying an entry in said second entity.

7. A system for translating a query language as recited in claim 6, wherein said third entity having a field for identifying the position of said entity identified in the second field.

8. A system for translating a query language as recited in claim 5, wherein said first field of said third entity is equivalent to a content in the identification field of said first entity.

9. A system for translating a query language as recited in claim 5, wherein said first field of said third entity is equivalent to a content in the identification field of said second entity.

10. A system for translating a query language as recited in claim 5, wherein said first field of said third entity is a key to the first entity connecting said third entity to said first entity.

11. A system for translating a query language as recited in claim 5, wherein said first field of said third entity is a key to the second entity connecting said third entity to said second entity.

12. A system for translating a query language as recited in claim 5, wherein said first entity further comprising a key linking said first entity to said second entity.

13. A system for translating a query language as recited in claim 12, wherein said second entity further including a key linking said second entity to said third entity.

14. A system for translating a query language as recited in claim 13, wherein said first entity is indirectly linked to said third entity via said second entity.

16. A method of translating a query as recited in claim 15, after assigning the table and column further comprising:

resolving a predicate into a condition and entering the condition into a condition list for each predicate in the query.

18. A method of translating a query as recited in claim 17, after assigning the table and column further comprising:

resolving a predicate into a condition and entering the condition into a condition list for each predicate in the query.

15. A method of translating a query based on a resource-property modelstring into a statement for querying a relational database, wherein the resource-property having at least one rule and said query having at least one rule string, comprising:

providing at least one resource in said model;

providing at least one property in each resource;

substituting the rule string for a rule property in the resource-property query;

assigning a relational table having an ID to the resource and entering the assigned table ID into a table list for each resource and resource property in the query;

determining any link element based on the resource property and entering the link element into a link list for each resource property in the query;

assigning a table and column to a primitive property and entering the table and column into a column list for each primitive property in the query; and

forming a relational query statement from the column list, the table list and the link list.

17. A method of translating a query based on a resource-property modelstring into a statement for querying a relational database, wherein the resource-property having at least one rule and said query having at least one rule string, comprising:

providing at least one resource in said model;

providing at least one property in each resource;

substituting the rule string for a rule property derived from the resource-property query;

assigning a relational table having an ID to the resource and entering the assigned table ID into a table list for each resource and resource property derived from the query;

determining any link element based on the resource property and entering the link element into a link list for each resource property derived from the query;

assigning a table and column to a primitive property and entering the table and column into a column list for each primitive property derived the query; and

forming a relational query statement from the column list, the table list and the link list.

19. A computer program product embodying a program of instructions executable by a machine to perform method steps for translating a query based on a resource-property model having a rule string into a statement for querying a relational database, wherein the resource-property having at least one rule and said query having at least one rule string, comprising:

substituting the rule string for the rule property for each rule property in or derived from the resource-property query;

assigning a relational table having an ID to the resource or resource property and entering the assigned table id into a table list for each resource and resource property in or derived from the query;

determining any implied conditions based on the resource property and entering the implied conditions into a condition list for each resource property in or derived from the query;

assigning a table and column to the primitive property and entering the table and column into a column list for each primitive property in or derived from the query;

resolving the predicate into one or more conditions and entering the one or more conditions into the condition list for each predicate in or derived from the query; and

forming an a relational query statement from the column list, the table list and the condition list.