The example your mentioning does not provide enough information to grasp the powerfull nature of SQLMaps. It's fine to get a high level understanding of how iBatis deals with statements.
As you probably know, SQL in iBatis is built using XML. Tags are used to test different conditions on the parameter object. So for example, you can test whether a value in the parameter is null, equal to some value and so on. These tags allows for building complex SQL queries that are easy to read, understand and especially maintain. So instead of concatenating Java String objects to build complex queries with a bunch of if-then-else and switch-case statements, you build the query by specifying when/how certain blocks should be evaluated. I suggest you read the SQLMap PDF document to get a better glimpse of what iBatis SQL Maps can really help you accomplish. Thanks, Philippe -----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Monday, November 29, 2004 5:05 PM To: [EMAIL PROTECTED] Subject: Re: A few dumb questions On Mon, 29 Nov 2004 13:30:26 -0500, Philippe Laflamme <[EMAIL PROTECTED]> wrote: > As an example, my use of the iBatis framework allows me to have a > single statement that can update a single row or multiple rows in a > table based on the state of the object being updated. By looking at > the state of the object, the resulting SQL UPDATE statement can modify > many columns or a single one. Also, using the same paradigm, I'm able > to build complex queries that "JOIN" on different tables depending on > the object that describes a search criteria. The same SQL Map could > JOIN on any number of tables depending on its input object. Could you explain this a little bit more? You know I am a newbie and am not sure I can follow you here. What I have understood this far is the example on http://ibatis.com/common/example.html Thanks, Oliver
