Hi Mark,
thanks again.
In the meanwhile I've found another solution to my problem. I use the
function "documentExists" from the ArangoCollection object.
So I don't have to evaluate the error numbers anymore to find exceptions
thrown for duplicate document-/edge-keys.
Best regards
Christoph
Am
Yes.
But I added this to my todo list. Maybe I can implement something for the
next release.
Best
Mark
Am Mittwoch, 30. November 2016 11:42:54 UTC+1 schrieb Christoph Engel:
>
> Hi Mark,
>
> thanks for your reply. Does that mean I have to parse the error message
> string to get the code?
>
> be
Hi Mark,
thanks for your reply. Does that mean I have to parse the error message
string to get the code?
best regards
Christoph
Am Mittwoch, 30. November 2016 09:18:22 UTC+1 schrieb mpv1989:
>
> Hi Christoph,
>
> in version 4.1.2 every information of the error is part of the
> exception.erroM
Hi Christoph,
in version 4.1.2 every information of the error is part of the
exception.erroMessage.
The format is:
"Response: {errorCode}, Error: {errorNumber} - {errorMessage}"
If no error occurs but the responseCode is 300 or above the errorMessage
only contains:
"Response Code: {responseCod
