Error on batch execute request is not propagated.

[kadishmal]

During concurrent batch execute requests if the parallel requests cause a deadlock, CUBRID intelligently decides which of the requests should be killed so that the rest transactions could continue.

If a batch transaction is failed due to a deadlock the following error code and message is returned however node-cubrid doesn't detect it as an error so the error is not propagated to the user.

Error: -72:Your transaction (index 97, DBA@db-host|16337) has been unilaterally aborted by the system.

The response message must be interpreted properly as an error and returned to a user.

A safe suggestion to a user is to retry the operation.