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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/10/19 00:08:50 UTC
[jira] Issue Comment Edited: (DERBY-3135) TableFunctionTest fails
with weme6.1 on trunk
[ https://issues.apache.org/jira/browse/DERBY-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536059 ]
rhillegas edited comment on DERBY-3135 at 10/18/07 3:08 PM:
----------------------------------------------------------------
Hi Dan,
Yes, the test assumes that Derby will call getBigDecimal() when retrieving a DECIMAL value from a table function. In fact, the test is enforcing this behavior so that our user documentation can be kept in sync with Derby's actual behavior. What this says to me is that the user documentation needs to say that on small device platforms, Derby calls getString() on DECIMAL columns in table functions. And the test needs to be changed to enforce this behavior. Thanks for running the test on this platform and catching this.
was (Author: rhillegas):
Hi Mamta,
Yes, the test assumes that Derby will call getBigDecimal() when retrieving a DECIMAL value from a table function. In fact, the test is enforcing this behavior so that our user documentation can be kept in sync with Derby's actual behavior. What this says to me is that the user documentation needs to say that on small device platforms, Derby calls getString() on DECIMAL columns in table functions. And the test needs to be changed to enforce this behavior. Thanks for running the test on this platform and catching this.
> TableFunctionTest fails with weme6.1 on trunk
> ---------------------------------------------
>
> Key: DERBY-3135
> URL: https://issues.apache.org/jira/browse/DERBY-3135
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.4.0.0
> Environment: IBM weme6.1 jdk
> Reporter: Mamta A. Satoor
> Assignee: Rick Hillegas
> Attachments: derby-3135-01-jsr169numerics-aa.diff
>
>
> TableFunctionTest fails with weme6.1 with following 2 failures.
> 1st failure
> noSpecialCollation(org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest)junit.framework.ComparisonFailure:
> expected:<...BigDecimal getDouble getDouble getFloat getDouble getInt
> getString getBytes getBigDecimal...> but was:<...String getDouble
> getDouble getFloat getDouble getInt getString getBytes getString...>
> at java.lang.Throwable.<init>(Throwable.java:57)
> at java.lang.Throwable.<init>(Throwable.java:68)
> at junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
> at junit.framework.ComparisonFailure.<init>(ComparisonFailure.java:19)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.checkGetXXXCalls(TableFunctionTest.java:1205)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.allLegalDatatypesVTIResults(TableFunctionTest.java:1139)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.tableFunctionTest(TableFunctionTest.java:893)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.noSpecialCollation(TableFunctionTest.java:869)
> at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:205)
> at <unknown class>.<unknown method>(Unknown Source)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
> 2nd failure
> specialCollation(org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest)junit.framework.ComparisonFailure:
> expected:<...BigDecimal getDouble getDouble getFloat getDouble getInt
> getString getBytes getBigDecimal...> but was:<...String getDouble
> getDouble getFloat getDouble getInt getString getBytes getString...>
> at java.lang.Throwable.<init>(Throwable.java:57)
> at java.lang.Throwable.<init>(Throwable.java:68)
> at junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
> at junit.framework.ComparisonFailure.<init>(ComparisonFailure.java:19)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.checkGetXXXCalls(TableFunctionTest.java:1205)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.allLegalDatatypesVTIResults(TableFunctionTest.java:1139)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.tableFunctionTest(TableFunctionTest.java:893)
> at org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.specialCollation(TableFunctionTest.java:879)
> at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:205)
> at <unknown class>.<unknown method>(Unknown Source)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.