Skip to main content

Learning iBATIS - The SqlMap API

The SqlMapClient interface has over 30 methods on it.

#1 The queryForObject() methods

The queryForObject() methods are used to get a single row from the database
into a Java object, and come with two signatures:
■ Object queryForObject(String id, Object parameter) throws SQLException;
■ Object queryForObject(String id, Object parameter, Object result)
throws SQLException;


The second form is useful if you have an object that cannot be easily
created because of a protected constructor or the lack of a default constructor.


#2 The queryForList() methods
The queryForList() methods are used to get one or more rows from the database
into a List of Java objects, and like queryForObject(), they also come in two versions:
■ List queryForList(String id, Object parameter) throws SQLException;
■ List queryForList(String id, Object parameter, int skip, int max)
throws SQLException;

#3 The queryForMap() methods
The queryForMap() methods return a Map (instead of a List) of one or more rows
from the database as Java objects. Just like the other query methods, it has two
forms as well:

■ Map queryForMap(String id, Object parameter, String key) throws SQLException;
■ Map queryForMap(String id, Object parameter, String key, String value)
throws SQLException;

By using the first method, you could create a Map that had the key
property as the key to the map and the full  bean as the value. Using
the second method, you could create a Map that had the key property as
the key to the map, and only the value as the value.

#4 The insert method
As you may have guessed, the insert method is used to execute mapped statements that correspond to the SQL insert statement:

Object insert(String id, Object parameterObject) throws SQLException;
e.g.

<insert id="insertWithInlineInfo">
insert into account (
accountId,
username, password,
memberSince,
firstName, lastName,
address1, address2,
city, state, postalCode,
country, version
) values (


#accountId:NUMBER#,
#username:VARCHAR#, #password:VARCHAR#,
#memberSince:TIMESTAMP#,
#firstName:VARCHAR#, #lastName:VARCHAR#,
#address1:VARCHAR#, #address2:VARCHAR#,
#city:VARCHAR#, #state:VARCHAR#, #postalCode:VARCHAR#,
#country:VARCHAR#, #version:NUMBER#
)
</insert>

Codes;

Account account = new Account();
account.setAccountId(new Integer(9999));
account.setUsername("inlineins");
account.setPassword("poohbear");
account.setFirstName("Inline");
account.setLastName("Example");
sqlMapClient.insert("Account.insertWithInlineInfo", account);




#5 The update method
The update method is used to execute mapped statements that correspond to SQL update statement:

int update(String id, Object parameterObject) throws SQLException;

#6 The delete method
The delete method is almost identical to the update method, but instead of being used to execute update SQL statements, it is used to execute delete statement:

int delete(String id, Object parameterObject) throws SQLException;








Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.


Symptom: 1.The JVM became Out of memory when creating big consumption report 2.Those JRTemplateElement-instances is still there occupied even if I logged out the system
Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.The clearobjects() method in ReportThread class has not been triggered when logging out
Action I tried:      About the Virtualizer: 1.Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory     About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object                Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateE…