Hi,
When using the transactional endpoint, when an error occurs, such as for
instance a unique constraint violation, the status code returned is still
200. Is this by design? Is the preferred method to always have to examine
errors property in body to make sure it's empty to guarantee success?
Yes it is, as the results are streamed, the headers are already sent out
immediately before query execution happens.
Also as you can send many queries, the error contains more information on which
(the last) query it happened.
There is an error field in the response.
Not sure how much effort
