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 "Anurag Shekhar (JIRA)" <de...@db.apache.org> on 2006/02/20 14:08:25 UTC
[jira] Created: (DERBY-1013) jdbc4 test suite test classes are
using Util.notImplemented
jdbc4 test suite test classes are using Util.notImplemented
-----------------------------------------------------------
Key: DERBY-1013
URL: http://issues.apache.org/jira/browse/DERBY-1013
Project: Derby
Type: Bug
Reporter: Anurag Shekhar
jdbc4 test suite test classes are using Util.notImplemented to get exception text and then using the message comparison to check if the message are same in the thrown exception. This may cause problem in future because the jdbc4 code is using SQLState.NOT_IMPLEMENTED with a paramter (feature name). As the test classes are creating the exception without any parameter the test comparision will fail.
In this patch I have modified the test code to test for sql state which won't change.
--
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
[jira] Updated: (DERBY-1013) jdbc4 test suite test classes are
using Util.notImplemented
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Kathey Marsden updated DERBY-1013:
----------------------------------
Component: Test
> jdbc4 test suite test classes are using Util.notImplemented
> -----------------------------------------------------------
>
> Key: DERBY-1013
> URL: http://issues.apache.org/jira/browse/DERBY-1013
> Project: Derby
> Type: Bug
> Components: Test
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: derby-1013.diff
>
> jdbc4 test suite test classes are using Util.notImplemented to get exception text and then using the message comparison to check if the message are same in the thrown exception. This may cause problem in future because the jdbc4 code is using SQLState.NOT_IMPLEMENTED with a paramter (feature name). As the test classes are creating the exception without any parameter the test comparision will fail.
> In this patch I have modified the test code to test for sql state which won't change.
--
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
[jira] Assigned: (DERBY-1013) jdbc4 test suite test classes are
using Util.notImplemented
Posted by "Anurag Shekhar (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Anurag Shekhar reassigned DERBY-1013:
-------------------------------------
Assign To: Anurag Shekhar
> jdbc4 test suite test classes are using Util.notImplemented
> -----------------------------------------------------------
>
> Key: DERBY-1013
> URL: http://issues.apache.org/jira/browse/DERBY-1013
> Project: Derby
> Type: Bug
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
>
> jdbc4 test suite test classes are using Util.notImplemented to get exception text and then using the message comparison to check if the message are same in the thrown exception. This may cause problem in future because the jdbc4 code is using SQLState.NOT_IMPLEMENTED with a paramter (feature name). As the test classes are creating the exception without any parameter the test comparision will fail.
> In this patch I have modified the test code to test for sql state which won't change.
--
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
[jira] Resolved: (DERBY-1013) jdbc4 test suite test classes are
using Util.notImplemented
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Rick Hillegas resolved DERBY-1013:
----------------------------------
Resolution: Fixed
Good step forward. Patch touches only jdbc 4 tests. They run cleanly. Committed with subversion revision 379634.
> jdbc4 test suite test classes are using Util.notImplemented
> -----------------------------------------------------------
>
> Key: DERBY-1013
> URL: http://issues.apache.org/jira/browse/DERBY-1013
> Project: Derby
> Type: Bug
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: derby-1013.diff
>
> jdbc4 test suite test classes are using Util.notImplemented to get exception text and then using the message comparison to check if the message are same in the thrown exception. This may cause problem in future because the jdbc4 code is using SQLState.NOT_IMPLEMENTED with a paramter (feature name). As the test classes are creating the exception without any parameter the test comparision will fail.
> In this patch I have modified the test code to test for sql state which won't change.
--
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
[jira] Updated: (DERBY-1013) jdbc4 test suite test classes are
using Util.notImplemented
Posted by "Anurag Shekhar (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Anurag Shekhar updated DERBY-1013:
----------------------------------
Attachment: derby-1013.diff
changed the jdbc4 test classes to compare sql state and not.
> jdbc4 test suite test classes are using Util.notImplemented
> -----------------------------------------------------------
>
> Key: DERBY-1013
> URL: http://issues.apache.org/jira/browse/DERBY-1013
> Project: Derby
> Type: Bug
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: derby-1013.diff
>
> jdbc4 test suite test classes are using Util.notImplemented to get exception text and then using the message comparison to check if the message are same in the thrown exception. This may cause problem in future because the jdbc4 code is using SQLState.NOT_IMPLEMENTED with a paramter (feature name). As the test classes are creating the exception without any parameter the test comparision will fail.
> In this patch I have modified the test code to test for sql state which won't change.
--
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