ConstraintViolationException

The name of the column associated with the constraint violation, if available.

The specific name of the constraint that was violated, if available.

The primary error message the database raised.

Additional, human-readable details about the violation provided by the database. For a unique violation this is where the offending key and value appear.

Where this happened, innermost first, appended to by each layer as the exception unwinds. It is on the base class for the same reason queryContext is: adding to it is the only thing a frame can do to an exception without replacing it, and replacing one costs the type the caller catches on - a ConstraintViolationException restated as something else stops being the failure a retry looks for. A mapper walking a nested composite appends the attribute it was on, a transaction plan the step and parameter it was resolving. Rendered reversed, outermost first, so PATH: step 1 -> parameter 'name' -> map #1 reads from the plan down to the lambda.

The context of the query that resulted in this exception, if applicable.

The specific type of constraint violation mapped from the database error.

The name of the schema containing the table where the violation occurred, if available.

The raw error message received from the database, if applicable.

The SQL state code associated with the error, if applicable.

The name of the table where the constraint violation occurred, if available.

The call stack the violation arose in, for one raised inside a trigger or function.

Finds the Octavius failure behind this throwable, if there is one.

Provides a detailed, human-readable description of the error.