Repository navigation
jdbc: support categorized exceptions and SQLSTATE codes #119
Description
Return sqlStateSQL or sqlStateSQL99 (they are equal) from
DatabaseMetaData.getSQLStateType(). Now the value is 0, which is not correct.
Use SQLSTATE codes in SQLException where appropriate.
Use categorized SQL exceptions where possible:
- SQLNonTransientException
- SQLTransientException
- SQLRecoverableException
Consider also using of BatchUpdateException and SQLClientInfoException.
Test all this new stuff.
See also: https://docs.oracle.com/javase/tutorial/jdbc/basics/sqlexception.html
This issue is mostly optional (AFAIU), but DatabaseMetaData.getSQLStateType() should provide a correct value.
Activity
jdbc: add support for a result set holdability
jdbc: add support for a result set holdability
Add support for JDBC result set type
Add support for a result set type and concurrency
Add support for a result set type and concurrency
Raise SQLException on methods of a closed Connection
Raise SQLException on methods of a closed Connection
Raise SQLException on methods of a closed Connection
Raise SQLException on methods of a closed Connection
Add support for a result set type and concurrency
Add support for a result set type and concurrency
Raise SQLException on methods of a closed Connection
Add support for a result set type and concurrency
Add support for a result set type and concurrency
Raise SQLException on methods of a closed Connection
Raise SQLException on methods of a closed Connection
Totktonada commentedon Oct 17, 2019
We use
sqlStateSQLcodes now, butDatabaseMetaData.getSQLStateType()still returns 0. I think we should returnsqlStateSQLhere and close this issue.As I see from other JDBC implementations (mysql-connector-j, mariadb-connector-j, pgjdbc), it seems we don't obligated to set an sqlstate code for each thrown SQLException.
See also https://bugs.mysql.com/bug.php?id=3520
jdbc: support for DatabaseMetaData.getSQLStateType
jdbc: support for DatabaseMetaData.getSQLStateType