Possible Inconsistent Error Messages

[estephan]

Can someone please help me understand why the error handler is used in some cases and not in others?

I have a table named user which has a unique column named email.
If I create a new user with a duplicate email the error from feathers-objection looks something like this:

className: 'conflict'
code: 409
data: {columns: Array(1), table: 'user', constraint: 'user_email_unique'}
errors: {}
hook: {type: 'before', arguments: Array(2), service: {…}, app: ƒ, method: 'create', …}
message: 'email must be unique'
name: 'Conflict'
Symbol(feathers-knex/error):
UniqueViolationError: insert into "user" ("_createdById", "_entityOfId", "_fullTextSearch", "_updatedById", "createdAt", "displayName", "email", "updatedAt") values ($1, $2, $3, $4, $5, $6, $7, $8) returning "_id" - duplicate key value violates unique constraint "user_email_unique"\n ...

However, if I edit an existing user to change the email to a value that already exists in the DB, I get an error that looks something like this:

client: 'postgres'
columns: (1) ['email']
constraint: 'user_email_unique'
hook: {type: 'before', arguments: Array(3), service: {…}, app: ƒ, method: 'patch', …}
name: 'UniqueViolationError'
nativeError: error: update "user" set "email" = $1, "updatedAt" = $2 where "two"."_id" = $3 - duplicate key value violates unique constraint "user_email_unique"\n ...
schema: undefined
table: 'user'
__proto__: ConstraintViolationError
message: 'update "user" set "email" = $1, "updatedAt" = $2 where "user"."_id" =...

This seems to happen when _patch is called and this query is hit. Making the change to add .catch(errorHandler); at the end of that statement seems to give the desired result but is there another reason why we don't call errorHandler there?