Note that in some cases, certain methods return status values without issuing an exception. This occurs in situations that are not normally considered an error, but when some informational status is returned. For example, {@link com.sleepycat.db.Database#get Database.get} returns {@link com.sleepycat.db.OperationStatus#NOTFOUND OperationStatus.NOTFOUND} when arequested key does not appear in the database.
Exceptions thrown by BDB JE fall into three categories.
{@link OperationFailureException} and {@link EnvironmentFailureException}are the only two direct subclasses of {@code DatabaseException}.
(Actually the above statement is not strictly correct. {@link EnvironmentFailureException} extends {@link RunRecoveryException} whichextends {@code DatabaseException}. {@link RunRecoveryException} exists forbackward compatibility and has been deprecated. {@link EnvironmentFailureException} should be used instead.)
Note that in some cases, certain methods return status values without issuing an exception. This occurs in situations that are not normally considered an error, but when some informational status is returned. For example, {@link com.sleepycat.je.Database#get Database.get} returns {@link com.sleepycat.je.OperationStatus#NOTFOUND OperationStatus.NOTFOUND} when arequested key does not appear in the database.
Purpose: Wrapper for any database exception that occurred through EclipseLink.
This class inherits {@link RuntimeException}, so all exceptions are unchecked. @author Karl Gustafsson @since 1.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|