System, method, and program for applying query rewrite technology to object building

• US 6,134,540 A
• Filed: 05/09/1997
• Issued: 10/17/2000
• Est. Priority Date: 05/09/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation, S-B Power Tool Company (Robert Bosch GmbH)
• Original Assignee: International Business Machines Corporation
• Inventors: Kiernan, Gerald G., Carey, Michael J.
• Primary Examiner(s): Alam, Hosain T.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US08/853,294
• Time in Patent Office: 1,257 Days
• Field of Search: 707/4, 707/2, 707/3, 704/4
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24547 Optimisations to support specific applications; Extensibility of optimisers
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

The system, method, and program of this invention enables an object language application (e.g., C++, JAVA, etc.,) to issue a query over a view and to receive back, as query results, handles to application type objects which can be further manipulated by the application. A view is defined herein as a collection of a view type, and a view type is defined as a class or type. Upon receipt of the query referencing a view type, a query engine generates a query plan that builds mock (i.e., proxy) application type objects in memory based upon the view types. The application can run methods on the application type objects or point to other application type objects from the handles, to the application objects, that are returned to the application; and these manipulations will be understood by the query engine. In a preferred embodiment, query rewrite optimizations are applied to the queries over views requiring object building in order to optimize the evaluation of the query and the building of view objects as query results. For example, when a query over a view is analyzed and it is determined that the query is not requesting a handle, and is not referencing a method, but only asks for values, no objects are built. Also, if a query traverses a reference type attribute, but the query can be transformed into a join or outer join operation between relational tables, then no object building is required. In these above described situations, the rewritten query can be pushed down to the database management system of the data source for resolution. If the query does request a handle or references a method, then some object building is required. However, query rewrite techniques can still be applied so that parts of the query are pushed down to the DBMS to minimize the number of objects that are built.

Claims

1. A query system comprising:

a query engine having a capability to build objects in a memory based upon a view type referenced in a query received from an application; and

means for applying query rewrite optimizations to the query referencing the view type, wherein the query rewrite optimizations determine which portions of the query to push down to a database at a second tier for resolution and which portions of the query are to be processed by the query engine at a first tier to build objects from the view types.

2. The system of claim 1 further comprising:

means for building objects if the query requests a handle; and

means for pushing down some of the predicates of the query to the database management system to restrict the results and thereby the number of objects that have to be built to resolve the query.

3. The system of claim 1 wherein the means for applying query rewrite optimizations further comprises:

means for analyzing the query to determine if the query requests a handle on an object or references a method.

4. The system of claim 1 further comprising:

means for giving all of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method.

5. The system of claim 1 wherein the means for applying query rewrite optimizations further comprises:

means for analyzing the query to determine if the query requests a handle on an object, or if the query references a method, or if the query raises a collation sequence issue.

6. The system of claim 1 further comprising:

means for giving part of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method; and

means for resolving a remaining part of the query that raises a collation sequence issue in the memory of the query engine.

7. The system of claim 1 wherein the means for applying query rewrite optimizations further comprises:

means for rewriting the query, if the query traverses a reference type attribute, into a join or outer join operation between relational tables; and

means for resolving the rewritten query without performing object building.

8. The system of claim 1 wherein the means for applying query rewrite optimizations further comprises:

means for submitting the rewritten query to a data source without object building if the query referencing the view type only requests values to be returned.

9. A query system comprising:

means for building objects in memory based upon a view type referenced in a query received from an application; and

means for applying query rewrite optimizations to the query referencing the view type, wherein the query rewrite optimizations determine which portions of the query to push down to a database at a second tier for resolution and which portions of the query are to be processed by the query engine at a first tier to build objects from the view types.

10. The query system of claim 9, wherein the means for applying query rewrite optimizations comprises:

means for restricting a result set, by a database where the data resides, for predicates that can be pushed down to the database;

means for building an object in memory, before applying remaining predicates, that cannot be pushed down, in object space if the remaining predicates involve a method, or if the remaining predicates involve a function that references objects as function arguments; and

means for applying the remaining predicates, that define the query'"'"'s results, in object space after retrieving complete sets of data referenced in the query.

11. A query system comprising:

means for receiving at the query system at a first tier a query that either invokes a method on a view type or requires a view type to be returned as a result;

means for determining at the query system which predicates in the query are to be pushed down to a database at a second tier to be resolved; and

means for applying at the query system the remaining predicates in the query in object space, which comprises determining which objects, based upon view type definitions of view types referenced by the query, are to be built by the query system.

12. A program having computer readable program code means on a computer usable medium, the program comprising:

means having a capability to build objects in a memory based upon a view type referenced in a query received from an application; and

means for applying query rewrite optimizations to the query referencing the view type, wherein the query rewrite optimizations determine which portions of the query to push down to a database at a second tier for resolution and which portions of the query are to be processed by the query engine at a first tier to build objects from the view types.

13. The program of claim 12 further comprising:

means for building objects if the query requests a handle; and

means for pushing down some of the predicates of the query to the database management system to restrict the results and thereby the number of objects that have to be built to resolve the query.

14. The program of claim 12 wherein the means for applying query rewrite optimizations further comprises:

means for analyzing the query to determine if the query requests a handle on an object or references a method.

15. The program of claim 12 further comprising:

means for giving all of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method.

16. The program of claim 12 wherein the means for applying query rewrite optimizations further comprises:

means for analyzing the query to determine if the query requests a handle on an object, or if the query references a method, or if the query raises a collation sequence issue.

17. The program of claim 12 further comprising:

means for giving part of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method; and

means for resolving a remaining part of the query that raises a collation sequence issue in the memory of the query engine.

18. The program of claim 12 wherein the means for applying query rewrite optimizations further comprises:

means for rewriting the query, if the query traverses a reference type attribute, into a join or outer join operation between relational tables; and

means for resolving the rewritten query without performing object building.

19. The program of claim 12 wherein the means for applying query rewrite optimizations further comprises:

means for submitting the rewritten query to a data source without object building if the query referencing the view type only requests values to be returned.

20. A program having computer readable program code means on a computer readable medium, the program comprising:

means for receiving at a query system at a first tier a query that either invokes a method on a view type or requires a view type to be returned as a result;

means for determining at the query system which predicates in the query are to be pushed down to a database at a second tier to be resolved; and

means for applying at the query system the remaining predicates in the query in object space, which comprises determining which objects, based upon view type definitions of view types referenced by the query, are to be built at the query system.

21. A method implemented in a query system, the method comprising:

providing a query engine having a capability to build objects in a memory based upon a view type referenced in a query received from an application; and

applying query rewrite optimizations to the query referencing the view type, wherein the query rewrite optimizations determine which portions of the query to push down to a database at a second tier for resolution and which portions of the query are to be processed by the query engine at a first tier to build objects from the view types.

22. The method of claim 21 further comprising:

building objects if the query requests a handle; and

pushing down some of the predicates of the query to the database management system to restrict the results and thereby the number of objects that have to be built to resolve the query.

23. The method of claim 21 wherein the step of applying query rewrite optimizations further comprises:

analyzing the query to determine if the query requests a handle on an object or references a method.

24. The method of claim 21 further comprising:

sending all of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method.

25. The method of claim 21 wherein the step of applying query rewrite optimizations further comprises:

analyzing the query to determine if the query requests a handle on an object, or if the query references a method, or if the query raises a collation sequence issue.

26. The method of claim 21 further comprising:

sending part of the query to a data source to resolve without performing any object building, even though the query references the view type, if the query does not request a handle on an object and if the query does not reference a method; and

resolving a remaining part of the query that raises a collation sequence issue in the memory of the query engine.

27. The method of claim 21 wherein the step of applying query rewrite optimizations further comprises:

rewriting the query, if the query traverses a reference type attribute, into a join or outer join operation between relational tables; and

resolving the rewritten query without performing object building.

28. The method of claim 21 wherein the step of applying query rewrite optimizations further comprises:

submitting the rewritten query to a data source without object building if the query referencing the view type only requests values to be returned.

29. A method implemented in a query system, the method comprising:

building objects in memory based upon a view type referenced in a query received from an application; and

applying query rewrite optimizations to the query referencing the view type, wherein the query rewrite optimizations determine which portions of the query to push down to a database at a second tier for resolution and which portions of the query are to be processed by the query engine at a first tier to build objects from the view types.

30. The method of claim 29, wherein the step of applying query rewrite optimizations further comprises:

restricting a result set, by a database where the data resides, for predicates that can be pushed down to the database;

building an object in memory, before applying remaining predicates, that cannot be pushed down, in object space if the remaining predicates involve a method, or if the remaining predicates involve a function that references objects as function arguments; and

applying the remaining predicates, that define the query'"'"'s results, in object space after retrieving complete sets of data referenced in the query.

31. A method implemented in a query system, the method comprising:

receiving at the query system at a first tier a query that either invokes a method on a view type or requires a view type to be returned as a result;

determining at the query system which predicates in the query are to be pushed down to a database at a second tier to be resolved; and

applying at the query system the remaining predicates in the query in object space, which comprises determining which objects, based upon view type definitions of view types referenced by the query, are to be built at the query system.