Calling a single-param SP

Hi everyone, New question If I have a stored proc that takes a single parameter...is this the right way to call it in the SQL Map XML? {call OWNER.APP.SP_NAME(?)} or should I be using a parameterClass='java.lang.String' instead of the parameterMap in the procedure tag? Confuse

RE: Deployment question

I think I found the source of my problem...Here's the solution for those that care: I had deployed all three jars with a "database.properties" file referenced by the dao.xml. This file lived in the top-level of each jar, so there was no distinction between Order vs. Catalog vs. Customer when the

Re: [Table field names VS. Object properties names]

Hi again! Thanks for the quick comment Larry. You're absolutely right, I does make sense at any level (Java/SQL)... I guess my brain took a short vacation... :^) Sorry for asking the obvious. Regards, Carlos - Original Message - From: "Larry Meadors" <[EMAIL PROTECTED]> To:

Re: Autocommit not properly handled in Ibatis.

With Oracle, commitRequired should be set to false. Oracle is actually very well behaved with iBATIS. It's just that commits/rollbacks are costly even when no changes were made. Your bigger concern is WebSpherethat has to be the craziest app server on earth. I only hope you're using the la

Re: Autocommit not properly handled in Ibatis.

Great! We started to use iBATIS 1.5 years ago and we are really happy with it ... but the most problematic thing until now was this AutoCommit = false in WebSphere environment - now we are using commitRequired and indeed our life is easier :) "Anyway, unless you're using Oracle, feel free to make

Re: Autocommit not properly handled in Ibatis.

No, absolutely not. It will either make one start/commit/end per method call to SQLClient (if you don't start a transaction) or just one that you call explicitly. The only exception is if you're using Lazy Loading, but that's totally within your control. iBATIS always attempts to use the most e

Re: Autocommit not properly handled in Ibatis.

Hi Clinton, Murphy's law is validated again: I am using Oracle :( If I am using in a method N SELECT queries with commitRequired=true, iBATIS makes N commit() (one at the end of each query), right? Do you have any clue / recommendation how to minimize this overhead using iBATIS + Oracle? Tha

Deployment question

Hi everyone, I have iBATIS in an application we've deployed into Weblogic. Things run nicely as unit tests, so I know I have the basic plumbing working... Here's where things get a little tricky--I have three separate CVS modules that are built as different jars. Each has its own properties f

Query Regarding Sub Query - to pass more than one paramete.

Hi, Topic: I want to pass more than one parameter to the sub query. Like, In the getCategory query, I need to pass 2 parameters. Is it possible? Could you please reply me ASAP (with example, if possible). Thanks in anticipation. Regards, Kashyap

Re: Query Regarding Sub Query - to pass more than one paramete.

There's an example on page 38 of the iBATIS developer's guide. Jeff Butler On 1/25/07, Shankhavara, Kashyap <[EMAIL PROTECTED]> wrote: Hi, Topic: I want to pass more than one parameter to the sub query. Like, ** ** ** ** ** * * In the *getCategory* query, I need to pass 2 param

Re: Autocommit not properly handled in Ibatis.

In hindsight I wish I had made the default commitRequired=true... I believe the only database that really suffers from unecessary commits is Oracle. The other RDBMS are actually pretty good about not incurring additional overhead, and in fact Sybase drivers I've used demand that either commit or

Re: Autocommit not properly handled in Ibatis.

Hi Koka, In case of iBATIS commitRequired=false, if you execute SELECT statements, they are grouped into a transaction that "is terminated by a call to either the method commit or the method rollback" ... because iBATIS never calls commit() or rollback() it means that iBATIS do not handle prop

Re: Autocommit not properly handled in Ibatis.

In iBATIS SELECT case, no commit or rollback is executed ... *Question:* How do you interpret this fact? Not sure what kind of interpretation you ask for ;) Again, if the code looks like (you can leave out startTransaction / commitTransaction in defaultAutocommit=true mode, as iBatis will

RE: Strange behaviour when column is null

Could you include the SQL Exception that you are receiving? Randy -Original Message- From: Jonathan Tse [mailto:[EMAIL PROTECTED] Sent: Thursday, January 25, 2007 4:47 AM To: user-java@ibatis.apache.org Subject: Strange behaviour when column is null Hi all, I exp

Strange behaviour when column is null

Hi all, I experienced a very strange problem with iBatis. Everything is fine until I add one more field named imagePath (String in java, varchar in Mysql) to the DB and the product POJO. If the field is null in MySQL , iBatis result a NestedSQLException. But a similar field called descript