If a unique constraint is violated an OrientDB.RequestError is thrown instead of WLValidationError as I'd expect. Actually it wouldn't have to be WLValidationError, but currently the error is of code E_UNKNOWN and that should be E_VALIDATION.
Error (E_UNKNOWN) :: Encountered an unexpected error
OrientDB.RequestError: Cannot index record user{******}: found duplicated key '*****@gmail.com' in index 'user.email' previously assigned to the record #15:2
If a unique constraint is violated an
OrientDB.RequestError
is thrown instead ofWLValidationError
as I'd expect. Actually it wouldn't have to beWLValidationError
, but currently the error is of codeE_UNKNOWN
and that should beE_VALIDATION
.