Required settings for running captured and non-captured SQL statements dynamically, and replacing captured statements

With these settings, pureQuery runs dynamically all of the SQL statements that are in a pureQueryXML file or runs alternative SQL statements that correspond to captured statements. If a statement is not in the pureQueryXML file, pureQuery runs it dynamically.
When you run your application with these settings, pureQuery checks whether a given SQL statement is already in the pureQueryXML file for the connection that the statement must run against. Then, pureQuery performs one of these actions:
  • If the statement is in the pureQueryXML file, pureQuery runs the statement dynamically.
  • If the statement is in the pureQueryXML file, does not use autogenerated keys, and has a corresponding alternative SQL statement, pureQuery runs the replacement SQL statement dynamically.
  • If the statement is not in the pureQueryXML file, pureQuery runs the statement dynamically.
Table 1. Required settings
Property Setting
enableDynamicSQLReplacement TRUE
pureQueryXml file-name.pdqxml or file-name.xml

In this combination of settings, pureQuery ignores the value of allowDynamicSQL.

This table does not show properties that you can leave at their default values or other properties that you might want to use. Here is a complete list of the properties that you can use when running SQL statements:

You can also set logging properties. See Descriptions of properties for logging and tracing.

See How to set properties for client optimization for information about how and where to set these properties.


Feedback