Getting Startedwith pureQuery

118
Getting Started with pureQuery
Figure 6.9 - The options file Default.genProps in a pureQuery-enabled project
When you save changes to Default.genProps, A dialogue like the one in Figure 6.10
might pop up with a warning message that indicates that the options you are specifying for
interfaces might have changed, and that you might need to rebuild your project for its
implementation classes to reflect your changes. The dialogue will ask if you want to rebuild
the project for the changes to take affect. This occurs because Default.genProps files
also specify options for generating implementation classes of interfaces in the pureQuery
annotated method style (Section 6.3). When you do not make changes to any of the
options that affect interfaces, you can select No on the dialogue.
Figure 6.10 - When you save changes to Default.bindProps, a dialogue asks if
you want to rebuild your project to reflect any changes.
6.6.2 Statement sets in pureQueryXml files
The Configure utility groups the SQL statements into statement sets. In a pureQueryXml
file, statementSet elements represent the statement sets. When the StaticBinder utility
binds a pureQueryXml file against IBM DB2 databases, packages in the database
correspond to statement sets in the pureQueryXml file. Because packages must have
unique names in the database, the Configure utility requires that you specify a root
package name that it will use to create the names of the packages. You specify the root
package name to the utility by using the option -rootPkgName.