🚀 Feature: Improve Database Exception Handling

[EVDOG4LIFE]

🔖 Feature description

When attempting to create a document that contains a non unique attribute on a collection that has a Unique index, you are given a misleading and generic error such as:

Failed to insert document: Document with the requested ID already exists. Try again with a different ID or use ID.unique() to generate a unique ID.

The enhancement here, will be to call out which attribute is causing the exception.

🎤 Pitch

When returning exceptions, we need to be verbose and provide which attribute is causing the conflict.

For example, I have a Unique index on a column named email. [email protected] is already taken, but when trying to create a new document with the same value, it should not return Failed to insert document: Document with the requested ID already exists. Try again with a different ID or use ID.unique() to generate a unique ID., but instead return something like Failed to insert document: Duplicate key {$id} violates unique constraint on {$key}. Try again with a different ID or use ID.unique() to generate a unique ID.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[7777chaitanya]

@EVDOG4LIFE , I am willing to take up this issue. Could you assign this to me, please?