org.springframework.dao
Class IncorrectUpdateSemanticsDataAccessException
java.lang.Object
java.lang.Throwable
java.lang.Exception
java.lang.RuntimeException
org.springframework.core.NestedRuntimeException
org.springframework.dao.DataAccessException
org.springframework.dao.InvalidDataAccessResourceUsageException
org.springframework.dao.IncorrectUpdateSemanticsDataAccessException
- All Implemented Interfaces:
- Serializable
- Direct Known Subclasses:
- JdbcUpdateAffectedIncorrectNumberOfRowsException
- public class IncorrectUpdateSemanticsDataAccessException
- extends InvalidDataAccessResourceUsageException
Data access exception thrown when something unintended appears to have
happened with an update, but the transaction hasn't already been rolled back.
Thrown, for example, when we wanted to update 1 row in an RDBMS but actually
updated 3.
- Author:
- Rod Johnson
- See Also:
- Serialized Form
IncorrectUpdateSemanticsDataAccessException
public IncorrectUpdateSemanticsDataAccessException(String msg)
- Constructor for IncorrectUpdateSemanticsDataAccessException.
- Parameters:
msg
- message
IncorrectUpdateSemanticsDataAccessException
public IncorrectUpdateSemanticsDataAccessException(String msg,
Throwable ex)
- Constructor for IncorrectUpdateSemanticsDataAccessException.
- Parameters:
msg
- messageex
- root cause from the underlying API, such as JDBC
wasDataUpdated
public boolean wasDataUpdated()
- Return whether data was updated.
If this method returns false, there's nothing to roll back.
The default implementation always returns true.
This can be overridden in subclasses.
getDataWasUpdated
public boolean getDataWasUpdated()
- Deprecated. in favor of
wasDataUpdated
- See Also:
wasDataUpdated()
Copyright (C) 2003-2004 The Spring Framework Project.