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 kiknadze@gmail.com designates
 209.85.219.171 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;
        b=qhsQmy+RoBwoYFpKUFrX9iNS0h/zOxff05Bf0DFWyTAXIMsb++ZfiYOr0DIslTbYz8
         JH5dN3coEfurbXwHO0HGodJMs46G8nGp5yl9R/RWjDvqu71dvsXDRe9ixzOHk+FnDxh1
         fDpbyflxDkma0i0H3FWBQqc1GKTMb6BBrXyT8=
MIME-Version: 1.0
In-Reply-To: <23521134.post@talk.nabble.com>
References: <23510359.post@talk.nabble.com>
	 <b230bcc10905130056s11968d55jb3d3d45379700145@mail.gmail.com>
	 <23521134.post@talk.nabble.com>
Date: Wed, 13 May 2009 17:01:46 +0400
Message-ID: <536e8800905130601u7c946b2bq44f9f3fce45ebc2a@mail.gmail.com>
Subject: Re: Identify the record that caused unique constraint violation
From: Nicholoz Koka Kiknadze <kiknadze@gmail.com>
To: user-java@ibatis.apache.org
Content-Type: multipart/alternative; boundary=0016367d69d858837c0469cad001

--0016367d69d858837c0469cad001
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

It may be database dependent. Here's extract from oracle docs
http://download.oracle.com/docs/cd/B10501_01/java.920/a96654/oraperf.htm


After a batch exception, the update counts array can be retrieved using the
getUpdateCounts() method of the BatchUpdateException object. This returns an
int array of update counts, just as the executeBatch() method does. In the
Oracle implementation of standard update batching, contents of the update
counts array are as follows after a batch exception:

   - For a prepared statement batch, it is not possible to know which
   operation failed. The array has one element for each operation in the batch,
   and each element has a value of -3. According to the JDBC 2.0 specification,
   a value of -3 indicates that an operation did not complete successfully. In
   this case, it was presumably just one operation that actually failed, but
   because the JDBC driver does not know which operation that was, it labels
   all the batched operations as failures.

   You should always perform a ROLLBACK operation in this situation.

--0016367d69d858837c0469cad001
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It may be database dependent. Here&#39;s extract from oracle docs <a href=
=3D"http://download.oracle.com/docs/cd/B10501_01/java.920/a96654/oraperf.ht=
m">http://download.oracle.com/docs/cd/B10501_01/java.920/a96654/oraperf.htm=
</a><br>
<br><br><p class=3D"BP">After a batch exception, the update counts array ca=
n be retrieved using the <code>getUpdateCounts()</code> method of the <code=
>BatchUpdateException</code> object. This returns an <code>int</code> array=
 of update counts, just as the <code>executeBatch()</code>
method does. In the Oracle implementation of standard update batching,
contents of the update counts array are as follows after a batch
exception:</p>

<ul class=3D"LB1"><li class=3D"LB1" type=3D"disc"><a name=3D"1057582"></a>F=
or a prepared
statement batch, it is not possible to know which operation failed. The
array has one element for each operation in the batch, and each element
has a value of -3. According to the JDBC 2.0 specification, a value of
-3 indicates that an operation did not complete successfully. In this
case, it was presumably just one operation that actually failed, but
because the JDBC driver does not know which operation that was, it
labels all the batched operations as failures. <p><a name=3D"1057836"></a><=
/p>

<p class=3D"BP1">You should always perform a <code>ROLLBACK</code> operatio=
n in this situation.</p>
</li></ul><br>

--0016367d69d858837c0469cad001--