- java.lang.Object
-
- java.lang.Throwable
-
- java.lang.Exception
-
- java.sql.SQLException
-
- java.sql.BatchUpdateException
-
- All Implemented Interfaces:
- Serializable, Iterable<Throwable>
public class BatchUpdateException extends SQLException
The subclass ofSQLException
thrown when an error occurs during a batch update operation. In addition to the information provided bySQLException
, aBatchUpdateException
provides the update counts for all commands that were executed successfully during the batch update, that is, all commands that were executed before the error occurred. The order of elements in an array of update counts corresponds to the order in which commands were added to the batch.After a command in a batch update fails to execute properly and a
BatchUpdateException
is thrown, the driver may or may not continue to process the remaining commands in the batch. If the driver continues processing after a failure, the array returned by the methodBatchUpdateException.getUpdateCounts
will have an element for every command in the batch rather than only elements for the commands that executed successfully before the error. In the case where the driver continues processing commands, the array element for any command that failed isStatement.EXECUTE_FAILED
.- Since:
- 1.2
- See Also:
- Serialized Form
-
-
Constructor Summary
Constructors Constructor and Description BatchUpdateException()
Constructs aBatchUpdateException
object.BatchUpdateException(int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenupdateCounts
.BatchUpdateException(int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givencause
andupdateCounts
.BatchUpdateException(String reason, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
andupdateCounts
.BatchUpdateException(String reason, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,cause
andupdateCounts
.BatchUpdateException(String reason, String SQLState, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
andupdateCounts
.BatchUpdateException(String reason, String SQLState, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,cause
, andupdateCounts
.BatchUpdateException(String reason, String SQLState, int vendorCode, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,vendorCode
andupdateCounts
.BatchUpdateException(String reason, String SQLState, int vendorCode, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,vendorCode
cause
andupdateCounts
.BatchUpdateException(Throwable cause)
Constructs aBatchUpdateException
object initialized with a givencause
.
-
Method Summary
Methods Modifier and Type Method and Description int[]
getUpdateCounts()
Retrieves the update count for each update statement in the batch update that executed successfully before this exception occurred.-
Methods inherited from class java.sql.SQLException
getErrorCode, getNextException, getSQLState, iterator, setNextException
-
Methods inherited from class java.lang.Throwable
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
-
-
-
-
Constructor Detail
-
BatchUpdateException
public BatchUpdateException(String reason, String SQLState, int vendorCode, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,vendorCode
andupdateCounts
. Thecause
is not initialized, and may subsequently be initialized by a call to theThrowable.initCause(java.lang.Throwable)
method.- Parameters:
reason
- a description of the errorSQLState
- an XOPEN or SQL:2003 code identifying the exceptionvendorCode
- an exception code used by a particular database vendorupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failure- Since:
- 1.2
-
BatchUpdateException
public BatchUpdateException(String reason, String SQLState, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
andupdateCounts
. Thecause
is not initialized, and may subsequently be initialized by a call to theThrowable.initCause(java.lang.Throwable)
method. The vendor code is initialized to 0.- Parameters:
reason
- a description of the exceptionSQLState
- an XOPEN or SQL:2003 code identifying the exceptionupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failure- Since:
- 1.2
-
BatchUpdateException
public BatchUpdateException(String reason, int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenreason
andupdateCounts
. Thecause
is not initialized, and may subsequently be initialized by a call to theThrowable.initCause(java.lang.Throwable)
method. TheSQLState
is initialized tonull
and the vender code is initialized to 0.- Parameters:
reason
- a description of the exceptionupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failure- Since:
- 1.2
-
BatchUpdateException
public BatchUpdateException(int[] updateCounts)
Constructs aBatchUpdateException
object initialized with a givenupdateCounts
. initialized by a call to theThrowable.initCause(java.lang.Throwable)
method. Thereason
andSQLState
are initialized to null and the vendor code is initialized to 0.- Parameters:
updateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failure- Since:
- 1.2
-
BatchUpdateException
public BatchUpdateException()
Constructs aBatchUpdateException
object. Thereason
,SQLState
andupdateCounts
are initialized tonull
and the vendor code is initialized to 0. Thecause
is not initialized, and may subsequently be initialized by a call to theThrowable.initCause(java.lang.Throwable)
method.- Since:
- 1.2
-
BatchUpdateException
public BatchUpdateException(Throwable cause)
Constructs aBatchUpdateException
object initialized with a givencause
. TheSQLState
andupdateCounts
are initialized tonull
and the vendor code is initialized to 0. Thereason
is initialized tonull
ifcause==null
or tocause.toString()
ifcause!=null
.- Parameters:
cause
- the underlying reason for thisSQLException
(which is saved for later retrieval by thegetCause()
method); may be null indicating the cause is non-existent or unknown.- Since:
- 1.6
-
BatchUpdateException
public BatchUpdateException(int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givencause
andupdateCounts
. TheSQLState
is initialized tonull
and the vendor code is initialized to 0. Thereason
is initialized tonull
ifcause==null
or tocause.toString()
ifcause!=null
.- Parameters:
updateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failurecause
- the underlying reason for thisSQLException
(which is saved for later retrieval by thegetCause()
method); may be null indicating the cause is non-existent or unknown.- Since:
- 1.6
-
BatchUpdateException
public BatchUpdateException(String reason, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,cause
andupdateCounts
. TheSQLState
is initialized tonull
and the vendor code is initialized to 0.- Parameters:
reason
- a description of the exceptionupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failurecause
- the underlying reason for thisSQLException
(which is saved for later retrieval by thegetCause()
method); may be null indicating the cause is non-existent or unknown.- Since:
- 1.6
-
BatchUpdateException
public BatchUpdateException(String reason, String SQLState, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,cause
, andupdateCounts
. The vendor code is initialized to 0.- Parameters:
reason
- a description of the exceptionSQLState
- an XOPEN or SQL:2003 code identifying the exceptionupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failurecause
- the underlying reason for thisSQLException
(which is saved for later retrieval by thegetCause()
method); may be null indicating the cause is non-existent or unknown.- Since:
- 1.6
-
BatchUpdateException
public BatchUpdateException(String reason, String SQLState, int vendorCode, int[] updateCounts, Throwable cause)
Constructs aBatchUpdateException
object initialized with a givenreason
,SQLState
,vendorCode
cause
andupdateCounts
.- Parameters:
reason
- a description of the errorSQLState
- an XOPEN or SQL:2003 code identifying the exceptionvendorCode
- an exception code used by a particular database vendorupdateCounts
- an array ofint
, with each element indicating the update count,Statement.SUCCESS_NO_INFO
orStatement.EXECUTE_FAILED
for each SQL command in the batch for JDBC drivers that continue processing after a command failure; an update count orStatement.SUCCESS_NO_INFO
for each SQL command in the batch prior to the failure for JDBC drivers that stop processing after a command failurecause
- the underlying reason for thisSQLException
(which is saved for later retrieval by thegetCause()
method); may be null indicating the cause is non-existent or unknown.- Since:
- 1.6
-
-
Method Detail
-
getUpdateCounts
public int[] getUpdateCounts()
Retrieves the update count for each update statement in the batch update that executed successfully before this exception occurred. A driver that implements batch updates may or may not continue to process the remaining commands in a batch when one of the commands fails to execute properly. If the driver continues processing commands, the array returned by this method will have as many elements as there are commands in the batch; otherwise, it will contain an update count for each command that executed successfully before theBatchUpdateException
was thrown.The possible return values for this method were modified for the Java 2 SDK, Standard Edition, version 1.3. This was done to accommodate the new option of continuing to process commands in a batch update after a
BatchUpdateException
object has been thrown.- Returns:
- an array of
int
containing the update counts for the updates that were executed successfully before this error occurred. Or, if the driver continues to process commands after an error, one of the following for every command in the batch:- an update count
Statement.SUCCESS_NO_INFO
to indicate that the command executed successfully but the number of rows affected is unknownStatement.EXECUTE_FAILED
to indicate that the command failed to execute successfully
- Since:
- 1.3
-
-
Deutsche Übersetzung
Sie haben gebeten, diese Seite auf Deutsch zu besuchen. Momentan ist nur die Oberfläche übersetzt, aber noch nicht der gesamte Inhalt.Wenn Sie mir bei Übersetzungen helfen wollen, ist Ihr Beitrag willkommen. Alles, was Sie tun müssen, ist, sich auf der Website zu registrieren und mir eine Nachricht zu schicken, in der Sie gebeten werden, Sie der Gruppe der Übersetzer hinzuzufügen, die Ihnen die Möglichkeit gibt, die gewünschten Seiten zu übersetzen. Ein Link am Ende jeder übersetzten Seite zeigt an, dass Sie der Übersetzer sind und einen Link zu Ihrem Profil haben.
Vielen Dank im Voraus.
Dokument erstellt 11/06/2005, zuletzt geändert 04/03/2020
Quelle des gedruckten Dokuments:https://www.gaudry.be/de/java-api-rf-java/sql/batchupdateexception.html
Die Infobro ist eine persönliche Seite, deren Inhalt in meiner alleinigen Verantwortung liegt. Der Text ist unter der CreativeCommons-Lizenz (BY-NC-SA) verfügbar. Weitere Informationen auf die Nutzungsbedingungen und dem Autor.
Referenzen
Diese Verweise und Links verweisen auf Dokumente, die während des Schreibens dieser Seite konsultiert wurden, oder die zusätzliche Informationen liefern können, aber die Autoren dieser Quellen können nicht für den Inhalt dieser Seite verantwortlich gemacht werden.
Der Autor Diese Website ist allein dafür verantwortlich, wie die verschiedenen Konzepte und Freiheiten, die mit den Nachschlagewerken gemacht werden, hier dargestellt werden. Denken Sie daran, dass Sie mehrere Quellinformationen austauschen müssen, um das Risiko von Fehlern zu reduzieren.