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/04/20 12:14:07 UTC
[jira] Updated: (DERBY-1198) jdbc/StatementTest.java uses SQLState
directly
[ http://issues.apache.org/jira/browse/DERBY-1198?page=all ]
Kristian Waagan updated DERBY-1198:
-----------------------------------
Attachment: derby-1198-rmimport.diff
'derby-1198-rmimport.diff' removes an unused import in StatementTest. After the new SQLStateConstants was introduced, SQLState is no longer used in the test.
I discovered this when planning to close the issue. After this tiny patch has been applied, the issue can be closed.
> 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: 10.2.0.0
> 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, e.g. SQLStateConstants.CONNECTION_EXCEPTION_CONNECTION_DOES_NOT_EXIST
--
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