[jira] [Commented] (DERBY-3181) isNullable on ResultSetMetaData from DatabaseMetaData.getBestRowIdentifier values are opposite when there is no rows in ResultSet vs. when there is a row.

[Danoja Dias (JIRA)]

    [ 
https://issues.apache.org/jira/browse/DERBY-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275839#comment-15275839
 ] 

Danoja Dias commented on DERBY-3181:
------------------------------------

Hi Bryan,
 
I am getting many failures like following. I have not added all of them here.  
Why do they differ from you?

<testcase 
classname="org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup" 
name="testOldVersion" time="0.035">
    <failure message="Old minor (driver):  expected:&lt;1&gt; but 
was:&lt;13&gt;" 
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
 Old minor (driver):  expected:&lt;1&gt; but was:&lt;13&gt;


<testcase 
classname="org.apache.derbyTesting.functionTests.tests.upgradeTests.Changes10_2"
 name="testDatabaseOwnerChange" time="0.042">
    <failure message="AUTHORIZATIONID not valid for SYSIBM 
expected:&lt;[DBA]&gt; but was:&lt;[APP]&gt;" 
type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: 
AUTHORIZATIONID not valid for SYSIBM expected:&lt;[DBA]&gt; but 
was:&lt;[APP]&gt;



  <testcase 
classname="org.apache.derbyTesting.functionTests.tests.upgradeTests.Changes10_4"
 name="testErrorMessage" time="0.327">
    <failure message="expected error while creating unique constraint over 
nullable column" 
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
 expected error while creating unique constraint over nullable column

> isNullable on ResultSetMetaData from DatabaseMetaData.getBestRowIdentifier 
> values are opposite when there is no rows in ResultSet vs. when there is a 
> row.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3181
>                 URL: https://issues.apache.org/jira/browse/DERBY-3181
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.4.1.3
>            Reporter: Myrna van Lunteren
>            Assignee: Danoja Dias
>            Priority: Trivial
>              Labels: derby_triage10_5_2
>         Attachments: Derby-3181.diff, repro.java, testChange.diff
>
>
> With code like the following: 
>            DatabaseMetaData dmd = conn.getMetaData(); 
>             ResultSet rs = dmd.getBestRowIdentifier(null,"APP","a",3,true);
>             ResultSetMetaData rsmd = rs.getMetaData(); 
>             int actualCols = rsmd.getColumnCount(); 
>             for (int i = 0; i < actualCols; i++) 
>             { 
>                  System.out.print("getColumnName: " + rsmd.getColumnName(i+1) 
> + ", isNullable: "); 
>                  System.out.println(rsmd.isNullable(i+1)); 
>             } 
> The printed values for isNullable returned are opposite of what they are when 
> the getBestRowIdentifier call looks like this:
>             ResultSet rs = dmd.getBestRowIdentifier(null,"APP","a",1,true);
> In the latter case, the values are:
> getColumnName: SCOPE, isNullable: 0
> getColumnName: COLUMN_NAME, isNullable: 1
> getColumnName: DATA_TYPE, isNullable: 0
> getColumnName: TYPE_NAME, isNullable: 1
> getColumnName: COLUMN_SIZE, isNullable: 0
> getColumnName: BUFFER_LENGTH, isNullable: 0
> getColumnName: DECIMAL_DIGITS, isNullable: 0
> getColumnName: PSEUDO_COLUMN, isNullable: 0
> In the first case, the values are:
> getColumnName: SCOPE, isNullable: 1
> getColumnName: COLUMN_NAME, isNullable: 0
> getColumnName: DATA_TYPE, isNullable: 1
> getColumnName: TYPE_NAME, isNullable: 1
> getColumnName: COLUMN_SIZE, isNullable: 1
> getColumnName: BUFFER_LENGTH, isNullable: 1
> getColumnName: DECIMAL_DIGITS, isNullable: 1
> getColumnName: PSEUDO_COLUMN, isNullable: 1
> The isNullable value should be stable. 
> It's probably worthwhile verifying what the value *should* be in the first 
> place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)