When pureQuery
searches for the value of a property, it searches the possible locations
in a particular order, depending on how the connection to the data
source is made.
When pureQuery finds a value
for a property, it stops looking for the value of that property in
other locations. If pureQuery does not find a value for a property,
it uses that property's default value.
If the connection is made
through a DataSource object of an application server, pureQuery searches
in the following order:
- pdq.name-of-data-source.properties file in
the application classpath
- pdq.appwide.properties in the application classpath
- The property pdqProperties, a comma-separated list, in a DataSource
object
- Global pdq.properties file in the middleware classpath
If the connection
is made through a DriverManager-based URL, pureQuery searches in the
following order:
- For DB2® and
IDS: pdqProperties string in a URL for a Connection object
- For DB2 and
IDS: Properties object that is passed as input to a getConnection()
method
- Global pdq.properties
file in the classpath.