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-1198) jdbc/StatementTest.java uses SQLState directly
Date Thu, 20 Apr 2006 14:15:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1198?page=all ]
Kristian Waagan closed DERBY-1198:

Ran the jdbc40 suite again to confirm the fix didn't break anything. Run passed.

> jdbc/StatementTest.java uses SQLState directly
> ----------------------------------------------
>          Key: DERBY-1198
>          URL: http://issues.apache.org/jira/browse/DERBY-1198
>      Project: Derby
>         Type: Bug

>   Components: Test
>     Reporter: David Van Couvering
>     Priority: Trivial
>      Fix For:
>  Attachments: derby-1198-rmimport.diff
> During inspection for another problem, I noticed that StatementTest.java still uses SQLState.NO_CURRENT_CONNECTION.
 SQLState is a private interface and should not be used in our tests.  This test  should instead
use "08003" or better yet use the new SQLStateConstants class in the functiontests/util package,

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