Getting Startedwith pureQuery

68
Getting Started with pureQuery
Figure 3.3 - Generating a pureQuery bean and interface from a database table
Click Next, and on the second page of the wizard you can select to generate a test
program to execute some of the generated CRUD (create, retrieve, update and delete)
methods of the annotated-method style interface you selected in the previous page. You
can also select the option to generate an inline-style class. These test programs can be
generated either as a class with a main method or as JUnits. For the test classes, you can
either select to include the connection information such as the database connection string
(url) and user ID or pass these two values as arguments. The password has to be passed
as an argument when executing your test class. For generating the bean, you can choose
to change the field names as required and get the mapping to the database automatically
generated for you. The pureQuery APIs, for example, use beans to hold the result of a
select statement—a bean represents a row/record in a database. You can also choose to
generate public fields or protected fields with public getters and setters. If you need custom
Java type mappings, you can simply change the default ones in the Bean Fields part of the
code generation wizard as shown in Figure 3.4, or use the @Handler annotation.