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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/11/17 22:40:44 UTC
[jira] Resolved: (DERBY-1617) Re-enable blobclob4BLOB clobTest6
that was disabled for an old bug
[ https://issues.apache.org/jira/browse/DERBY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-1617.
-----------------------------------
Resolution: Fixed
The test is enabled in the converted BlobClob4BlobTest
> Re-enable blobclob4BLOB clobTest6 that was disabled for an old bug
> ------------------------------------------------------------------
>
> Key: DERBY-1617
> URL: https://issues.apache.org/jira/browse/DERBY-1617
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Craig Russell
> Priority: Minor
>
> The jdbc api tests in org.apache.derbyTesting.functionTests.tests.jdbcapi.blobclob4BLOB.java have commented out clobTest6 due to an old bug that has apparently been fixed.
> line 1471:
> // 0 or negative position value
> if (isDerbyNet)
> System.out.println(" negative tests for clob.getSubstring won't run for network server until 5243 is fixed");
> if (! isDerbyNet)
> {
> The disabling code in the test should be removed, which will involve updating the canons to match.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.