Getting Startedwith pureQuery

138
Getting Started with pureQuery
7.2 Binding from interfaces and pureQueryXml files
You must specify pureQueryXml files or interfaces that contain the SQL statements that
pureQuery should bind.
7.2.1 Binding from interfaces
7.2.1.1 Database packages that the StaticBinder utility binds
For static SQL, interfaces of annotated methods represent packages in the database. The
implementation class corresponding to an interface has a root package name. The
StaticBinder utility uses this to determine the names of the packages in the database. The
root package name was specified to the Generator utility by using the -rootPkgName
option, or the Generator utility determined it based on the name of the interface, if the
option was not specified. In the implementation class, the root package name is stored in
the field identifier.
By default, the StaticBinder utility binds four packages in the database for each interface,
one at each of four isolation levels. Also by default, the StaticBinder utility appends 1, 2, 3,
and 4 to the root package name of the interface so that the four packages have distinct
names. The number 1 indicates the isolation level uncommitted read (UR), 2 indicates
cursor stability (CS), 3 indicates read stability (RS), and 4 indicates repeatable read (RR).
If you want the StaticBinder utility to bind only one package for an interface, specify the
option -isolationLevel. If you only want it to bind one package, and you do not want
the 1, 2, 3, or 4 indicator appended to the root package name, specify the option -
forceSingleBindIsolation to the Generator utility when you generate the
implementation class for the interface. The Generator utility needs to store this information
in the implementation class so that during static execution, pureQuery knows the names of
the packages. When you bind the interface, specify -isolationLevel so that the
StaticBinder utility will know which isolation level to use.
As an example, suppose that you have an interface with the root package name MYPKG.
Table 7.1 shows some example of the packages that the utility would bind in the database
for certain values of -forceSingleBindIsolation and -isolationLevel. The table
only shows the packages when the option -isolationLevel is either not specified, or is
specified with the value UR. The results follow the same pattern when other values are
specified for -isolationLevel.
Value specified for the
-forceSingleBindIsolation
option to the Generator utility
Value specified for the
-isolationLevel
option to the
StaticBinder utility
Names of
packages bound
in the database