Getting Startedwith pureQuery

128
Getting Started with pureQuery
If you are using IBM Optim Development Studio, you can add a replacement SQL
statement by opening a pureQueryXml file with the tool’s pureQueryXML Editor. Rightclick
on the statement that you want to replace and select Edit Statement, as shown in
Figure 6.14. Then, enter the new statement that you want to use, as shown in Figure 6.15.
Figure 6.14 - Edit a statement in a pureQueryXml file by using the pureQueryXML
Editor
Figure 6.15 - In the pureQueryXML Editor, type the replacement SQL statement that
you want to use
If you are not using IBM Optim Development Studio and you want to use this feature, you
will need to modify the pureQueryXml file directly. In a pureQueryXml file,
statementDescriptor elements describe the SQL statements that the application
executes. To replace an SQL statement, locate the statementDescriptor element for
that statement, and set the new SQL statement as the value of the processedSql
element. After you make changes to statement sets, for use in static execution, you must
set the value of their configureStatus attributes to REQUIRED.
If you specify to the StaticBinder utility a pureQueryXml file that contains replacement
statements, and the isBindable attributes are set to true for the statements, the utility
binds the alternate statements instead of the original statements. If you are using dynamic
SQL, pureQuery uses the original SQL statements by default. Use the pureQuery property
pdq.enableDynamicSQLReplacement to direct pureQuery to use the replacement SQL
statements. The value TRUE directs pureQuery to use the replacement SQL statements;
the value FALSE directs pureQuery to use the original SQL statements. The default value
is FALSE.
The ability to specify replacement SQL statements is a very powerful feature that can help
you to replace SQL statements in situations in which you cannot modify the source code.
Be aware, however, that using this feature can reduce the security of your application, if
you do not sufficiently protect the pureQueryXml file. Someone could maliciously add
replacement SQL statements to a pureQueryXml file to cause the application to execute
them instead of the SQL statements in the application. For SQL statements that execute