- 3.46.0 (latest)
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.1
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.1
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.27.1
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.2
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.1
- 3.14.1
- 3.13.0
- 3.12.1
- 3.11.1
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.1.1
- 2.0.0
- 1.19.3
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.1
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
The response for
ExecuteBatchDml][google.spanner.v1.Spanner.ExecuteBatchDml]
. Contains
a list of ResultSet][google.spanner.v1.ResultSet]
messages, one for
each DML statement that has successfully executed, in the same order
as the statements in the request. If a statement fails, the status in
the response body identifies the cause of the failure. To check for
DML statements that failed, use the following approach: 1. Check the
status in the response message. The
google.rpc.Code][google.rpc.Code]
enum value OK
indicates that
all statements were executed successfully. 2. If the status was not
OK
, check the number of result sets in the response. If the
response contains N
ResultSet][google.spanner.v1.ResultSet]
messages, then statement N+1
in the request failed. Example 1:
Request: 5 DML statements, all executed successfully. - Response: 5
ResultSet][google.spanner.v1.ResultSet]
messages, with the statusOK
. Example 2: - Request: 5 DML statements. The third statement has a syntax error. - Response: 2ResultSet][google.spanner.v1.ResultSet]
messages, and a syntax error (INVALID_ARGUMENT
) status. The number ofResultSet][google.spanner.v1.ResultSet]
messages indicates that the third statement failed, and the fourth and fifth statements were not executed.If all DML statements are executed successfully, the status is
OK
. Otherwise, the error status of the first failed statement.