This property can take these values:
The following table shows the capturedOnly, executionMode and allowDynamicSQL combinations and resulting operations:
capturedOnly | executionMode | allowDynamicSQL | SQL statement matched | Result |
---|---|---|---|---|
TRUE | STATIC | TRUE | YES | isBindable = True, Run the SQL statement statically isBindable = False, Run the SQL statement dynamically |
TRUE | STATIC/DYNAMIC | TRUE/FALSE | NO | Return an error |
TRUE | STATIC | FALSE | YES | isBindable = True, Run the SQL statement statically isBindable = False, Return an error |
TRUE | DYNAMIC | TRUE/FALSE | YES | Run the SQL statement |
FALSE | STATIC | TRUE | YES | isBindable = True, Run the SQL statement statically. isBindable = False, Run the SQL statement dynamically |
FALSE | STATIC | TRUE | NO | Run the SQL statement dynamically |
FALSE | STATIC | FALSE | YES | isBindable = True, Run the SQL statement statically. isBindable = False, Return an error |
FALSE | STATIC | FALSE | NO | Return an error |
FALSE | DYNAMIC | TRUE/FALSE | YES/NO | Run the SQL statement |
When using DB2® Call Level Interface (CLI) or the IBM® Data Server Driver with pureQuery Runtime, you can use the pureQuery Runtime property as a configuration keyword.
CLI applications that are enabled with pureQuery client optimization support only the pureQueryXml keyword to specify the file containing the captured SQL statements.
To ensure that Java applications with named parameter markers work correctly, regardless of the data server type and version, before you use named parameter markers in your applications, set the Connection or DataSource property enableNamedParameterMarkers to DB2BaseDataSource.YES.