Getting Startedwith pureQuery

Chapter 9 – Persistence Frameworks and Data Access: Context for pureQuery 175
INSERT INTO none getEmpno() Parameter marker name is a case
EMPLOYEE(EMPNO)
insensitive match to a field with a
VALUES :empno
public accessor method
Table 9.1 – Examples of default pureQuery bean mapping without annotations
Even though the pureQuery data access layer covers a wide variety of basic mappings by
default, there are cases when the user might want to override the default mapping
mechanism.. If so, the user will specify the mapping by using the Annotations described
above in the bean definition. Table 3.2 gives examples for using Annotations to override
the default pureQuery mapping mechanism:
sql property
of annotated
method
SELECT
FIRSTNM FROM
EMPLOYEE
SELECT
GOESBYNAME
FROM
EMPLOYEE
INSERT INTO
EMPLOYEE
(LASTNAME)
VALUES
(:lastname)
pureQuery bean Annotation
@Column (name=”firstnm”)
@ColumnOverride
(column=”goesbyname”,
propertyName=”firstName”)
@GeneratedKey
Bean field or
method
pureQuery mapping
rule
setFirstName() @Column annotation
specifies non default
mapping between a
result column name
and a property’s
public accessor
method using a case
insensitive match with
the result column
name
setFirstName() @ColumnOverride
annotation at the
bean class level
overrides any other
mappings
getEmpno()
Before an annotated
method with a bean
parameter returns, the
bean field
corresponding to the
@GeneratedKey
annotation will be
populated using the
value returned from
the database
Table 9.2 – Examples of pureQuery bean mapping using annotations