PrimaryKeyViolationError is needed

[vsnal]

Possible use case:
Inserting duplicate key into a many-to-many relation table with a composite primary key.
Unique constraint not work here.

[koskimas]

This could make sense. Which db did you test this on?

[koskimas]

Maybe we just need to make that case throw UniqueViolationError too instead of adding a new error type.

[vsnal]

Test on the MSSQL database:
error.nativeError.info = { number: 2627, state: 1, class: 14, message: 'Violation of PRIMARY KEY constraint '...'. Cannot insert duplicate key in object '...'. The duplicate key value is (1, 1).' }

Throw UniqueViolationError is an acceptable solution for that case.

[koskimas]

Thanks. If other databases throw UniqueViolationError in that case, I'll make MSSQL throw one too for consistency. If none of them do, maybe a separate PrimaryKeyViolationError is better.