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 jeffgbutler@gmail.com
 designates 209.85.210.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=b7fs3w+OZaB8PflDCEiKrxM5Q41hzjcFSB995e1RVflI5KeHdm7kFAFYVDZoeugKJ0
         Cxr6MYMRk/ZBtuL4+32686L8Y+rSzKqd9vOrlFI9r6EHFWiNhTaGj5NrJRW99Y4YNZrj
         D9LYBX8dd+i6ef6Due3p7TDbEEetq17vHMX+Y=
MIME-Version: 1.0
In-Reply-To: <C1394EEC9CD1A14B88F665C0833D959096C856@HH-XCLUSTER.spde.net>
References: <C1394EEC9CD1A14B88F665C0833D959096C856@HH-XCLUSTER.spde.net>
Date: Tue, 26 Jan 2010 20:30:50 -0600
Message-ID: <c593b8751001261830w2a09dbc5td9c33020a5b1cb07@mail.gmail.com>
Subject: Re: Strange data/number clobbered problem
From: Jeff Butler <jeffgbutler@gmail.com>
To: user-java@ibatis.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That's a really old version of iBATIS.  Look in the V2 developer's
guide for the "numericScale" attribute of a parameter map (either
inline or declared).  You'll need to upgrade to a newer version of
iBATIS to use it.  This will likely fix the problem.  Older versions
of iBATIS did not handle this properly.

Jeff Butler

On Tue, Jan 26, 2010 at 6:32 PM, Wu, Daniel <Daniel.Wu@smss.sony.com> wrote=
:
> Hi,
>
>
>
> We recently encountered some issues which potentially related to iBitis.
>
> We searched the web and the mailing list archive but did not find
> anything useful so far. =A0I am submitting this to the mailing list to se=
e
> if anyone has encountered this problem before and/or maybe point me some
> direction.
>
>
>
> We are using iBatis 2.1.7.597 or our production environment. =A0It is a
> java web application deployed to a farm of tomcat 5.5.27. =A0On one
> instance of the tomcat farm, the decimal point of numerical value was
> clobbered; the rest of the instances in the farm seems to be ok. =A0To
> troubleshoot, we isolated the instance and hot deployed new modified web
>
> app in the same tomcat container. =A0 =A0 =A0The modified app is compiled=
 from
>
> same branch of source code but we added some logging and a jsp page to
> allow us to run ad-hoc sql query.
>
>
>
> The modified app still shows the wrong numerical value, but the value is
> correct when we did direct sql execution through the jsp page. =A0We
> turned on the logging java.sql.* and saw the logging output that we
> believe is coming from iBatis:
>
>
>
> 2010-01-26 19:59:11,889 [TP-Processor6] DEBUG java.sql.ResultSet -
> {rset-100101} Result: [30453, New Releases $9.99 , 9.99 price for new
> releases, N, 0, 0.0, 2009-04-03 02:00:00.0, 2012-04-03 19:00:42.0,
>
> 2009-04-03 19:00:53.0, 2010-01-18 21:18:12.0, SSD]
>
>
>
> Where the 0.0 supposed to be 9.9. =A0The pattern of the issue is that the
> decimal point is shifted in the value, for example 15.95 becomes 159.5.
>
>
>
> We are currently stuck because we don't want to bounce the instance and
> we are not exactly sure how to trigger issue. =A0We can only suspect that
> there are some funny thing going on between iBatis and jdbc.
>
>
>
> Again, please let me know if you have seen this issue. =A0Thank you in
> advance.
>
>
>
> Daniel Wu
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>

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