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

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

Hi Bryan,

Are they running clean?
But I got something like this after adding the patch.

junit-core:
    [junit] Running org.apache.derbyTesting.junit.EnvTest
    [junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.987 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.derbynet._Suite
    [junit] Tests run: 339, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
863.906 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 127, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
200.987 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
25.368 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3226, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11,455.151 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 7881, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
5,330.829 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.store._Suite
    [junit] Tests run: 346, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3,127.492 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.engine._Suite
    [junit] Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
197.515 sec
    [junit] Running 
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationSuite
    [junit] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1,306.592 sec
    [junit] Running org.apache.derbyTesting.unitTests.junit._Suite
    [junit] Tests run: 170, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
47.173 sec
    [junit] Running 
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
    [junit] Tests run: 6439, Failures: 152, Errors: 35, Skipped: 0, Time 
elapsed: 8,246.18 sec
    [junit] Test 
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.suites.EncryptionSuite
    [junit] Tests run: 203, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
199.743 sec


> 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)

Reply via email to