Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26267056.post@talk.nabble.com>
Date: Mon, 9 Nov 2009 06:11:38 -0800 (PST)
From: fcarballo <fcarballo@gmail.com>
To: user-java@ibatis.apache.org
Subject: Re: Duplicate CacheKey with several query parameters value on null
 (IBATIS-663)
In-Reply-To: <25576546.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <25576546.post@talk.nabble.com>


Hey, no one found any solution to this? I really think that this is a serious
bug. I'm using an ad-hoc version of ibatis, with this class modified. But
I'll be glad to get this fix on a release version.


fcarballo wrote:
> 
> I'm having a problem with cached stored procedures call, using null
> parameters.
> When I call a stored procedure like: "call user.some_sp(?,?)" I get the
> same
> cacheKey for parameters: [1, null] and [null, 1]
> I think that the problem is in class
> com.ibatis.sqlmap.engine.exchange.BaseDataExchange on method getCacheKey:
> for (int i = 0; i < data.length; i++) {
>       if (data[i] != null) {
>         key.update(data[i]);
>       }
> }
> If the paramValue is null, it is ignored. Then when I get the cacheKey, on
> the parameters
>  values part, I get |1| for both parameters pair.
> 

-- 
View this message in context: http://old.nabble.com/Duplicate-CacheKey-with-several-query-parameters-value-on-null-%28IBATIS-663%29-tp25576546p26267056.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org