public class DeleteConstraintException extends SecondaryConstraintException
When using the base API (
com.sleepycat.je), this can occur when a
SecondaryDatabase is configured to be associated with a foreign key
SecondaryConfig.setForeignKeyDatabase(com.sleepycat.je.Database)), and is also
configured with the
ForeignKeyDeleteAction.ABORT delete action (see
SecondaryConfig.setForeignKeyDeleteAction(com.sleepycat.je.ForeignKeyDeleteAction)). Note that
is the default setting.
When using the DPL (
com.sleepycat.persist), this can occur when a
SecondaryKey is defined with a
DeleteAction.ABORT (which is the default).
Transaction handle is invalidated as a result of this
getExpirationTime, getPrimaryKey, getSecondaryDatabaseName, getSecondaryKey
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.