Getting Startedwith pureQuery

Chapter 4 – pureQuery tooling views 81
Figure 4.7 - Java Page
4.2.3.3 Database Packages
The Database Packages page groups all SQL statements by packages. If you were to bind
your application, this would be the same structure of the packages that you created on your
database.
Note:
The Database Package page may sometimes be empty while the other two pages show
some content. This may be due to your database not supporting static SQL and the
creation of database packages as is the case for projects associated with an IDS or Oracle
database connection. Another reason may be due to not having executed your application
using the Client Optimizer feature from the pureQuery runtime. After running your
application using the Client Optimizer, you would have gathered all statements and
configured them into packages needed to bind and for the creation of database packages
for static SQL execution.
Figure 4.8 shows two packages: one with one SQL statement that came from the execution
of a JDBC application, and the other from an interface generated by right-clicking on the
EMPLOYEE table and selecting Generate pureQuery Code… You can configure the
database packages before binding through the Default.genProps file. Use the
Default.bindProps file to specify options for determining how SQL statements are
bound into DB2 packages. These two files are found under the pureQueryFolder, refer
to the ODS build-in help for more details.