Getting Startedwith pureQuery

76
Getting Started with pureQuery
The pureQuery Analysis view gives developers the ability to drill down into the SQL
execution for “where used” analysis.
4.2 SQL Outline view
If your pureQuery enabled project contains the source code, you can gain insight and view
the statements on the SQL Outline that your application issues without having to execute
your application in capture mode—refer to Chapter 10 for more information on capturing
SQL statements. This is true for JPA, Hibernate, JDBC or any application that use the
pureQuery API. You may not see all of the SQL statements within your applications if you
have coded your statements based on variables and then passed those variables to the
JDBC methods, for example. In such cases, you may see the SQL Outline showing an
expression and not the actual SQL statement. You can get detailed help of the SQL Outline
at any time by selecting it and pressing F1 which will launch the build-in Help in ODS.
Figure 4.2 - SQL Outline view Java tab
4.2.1 Gather the SQL statements issued by the application
If your application is written using the pureQuery API, then the outline view will
automatically show all your SQL statements. However if your applications is coded directly
in JDBC and not in the pureQuery API, if you want to view all SQL statements issued by
your application to the database, then you will have to run your application using the Client
Optimizer feature from the pureQuery runtime. To leverage this feature, you must Enable
SQL capturing and binding for JDBC applications when either adding pureQuery support to
your project or from the project’s properties page as shown in Figure 4.3.