|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectjava.lang.Throwable
java.lang.Exception
java.lang.RuntimeException
org.springframework.core.NestedRuntimeException
org.springframework.dao.DataAccessException
org.springframework.dao.InvalidDataAccessResourceUsageException
org.springframework.jdbc.BadSqlGrammarException
Exception thrown when SQL specified is invalid. Such exceptions always have a java.sql.SQLException root cause.
It would be possible to have subclasses for no such table, no such column etc. A custom SQLExceptionTranslator could create such more specific exceptions, without affecting code using this class.
Constructor Summary | |
BadSqlGrammarException(java.lang.String task,
java.lang.String sql,
java.sql.SQLException ex)
Constructor for BadSqlGrammarException. |
Method Summary | |
java.lang.String |
getSql()
Return the SQL that caused the problem. |
java.sql.SQLException |
getSQLException()
Return the wrapped SQLException. |
Methods inherited from class org.springframework.core.NestedRuntimeException |
getCause, getMessage, printStackTrace, printStackTrace |
Methods inherited from class java.lang.Throwable |
fillInStackTrace, getLocalizedMessage, getStackTrace, initCause, printStackTrace, setStackTrace, toString |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
Constructor Detail |
public BadSqlGrammarException(java.lang.String task, java.lang.String sql, java.sql.SQLException ex)
task
- name of current task (may be null)sql
- the offending SQL statementex
- the root causeMethod Detail |
public java.sql.SQLException getSQLException()
public java.lang.String getSql()
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |