db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-1162) Add mechanism to assert/compare SQLStates
Date Wed, 29 Mar 2006 13:26:26 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1162?page=all ]
Kristian Waagan closed DERBY-1162:

Change verified.

> Add mechanism to assert/compare SQLStates
> -----------------------------------------
>          Key: DERBY-1162
>          URL: http://issues.apache.org/jira/browse/DERBY-1162
>      Project: Derby
>         Type: Sub-task
>   Components: Test
>     Versions:
>  Environment: JUnit test environment
>     Reporter: Kristian Waagan
>     Assignee: Kristian Waagan
>     Priority: Minor
>      Fix For:
>  Attachments: DERBY-1162-1a.diff
> The JUnit test environment needs a mechanism to assert/compare SQLStates. The goal is
to be able to reference states from SQLState without having to care if the length of the identifier
is 5,7 or more characters long.
> A way to do this already exist in StandardException.getSQLStateFromIdentifier, but it
is too unwieldy and long. I suggest adding  'assertSQLState(String, String, SQLException)'
method to BaseJDBCTestCase.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message