You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/03/29 14:18:23 UTC

[jira] Updated: (DERBY-1162) Add mechanism to assert/compare SQLStates

     [ http://issues.apache.org/jira/browse/DERBY-1162?page=all ]

Kristian Waagan updated DERBY-1162:
-----------------------------------

    Attachment: DERBY-1162-1a.diff

'DERBY-1162-1a.diff' adds method 'assertSQLState' to BaseJDBCTestCase.
Please review/commit.

> 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: 10.2.0.0
>  Environment: JUnit test environment
>     Reporter: Kristian Waagan
>     Assignee: Kristian Waagan
>     Priority: Minor
>  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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira