You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All requests against the transactional endpoint will return 200 or 201 status code, regardless of whether statements were successfully executed.
Neography not raising any errors make sense, as there is no error during the request. Nevertheless, letting a request silently fail does not seems a desired behaviour.
Currently, the solution is to read the errors array in the response returned when sending POST request to the transaction endpoint. Why not systematically raise an error when this array is not empty here ? It would be easy to catch (and silent if we don't care) but make it easier to spot bugs.
The text was updated successfully, but these errors were encountered:
Sending a invalid statements to the REST transaction endpoint does not raise errors.
According to Neo4j docs
Neography not raising any errors make sense, as there is no error during the request. Nevertheless, letting a request silently fail does not seems a desired behaviour.
Currently, the solution is to read the errors array in the response returned when sending POST request to the transaction endpoint. Why not systematically raise an error when this array is not empty here ? It would be easy to catch (and silent if we don't care) but make it easier to spot bugs.
The text was updated successfully, but these errors were encountered: