Skip to content

Standardize on an exception type for unique key constraint violations #215

@lrasku

Description

@lrasku

The Jakarta NoSQL javadocs currently promise for the various insert() overloads that:

If any entity of this type with the same unique identifier as any of the given entities already exists in the database and the database supports ACID transactions, then this method raises an error.

(Emphasis mine.) It would be useful for this error to also have a defined class, so that application code can catch-and-handle it separately from the (most likely unrecoverable) generic database I/O errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions