db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-2595) junit tests uses getExportedKeys with table name null
Date Fri, 27 Apr 2007 14:05:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jørgen Løland updated DERBY-2595:
---------------------------------

    Attachment: DERBY-2595-1.stat
                DERBY-2595-1.diff

Modified org/apache/derbyTesting/junit/JDBC#dropSchema. 

Instead of 
----------
rs = getExportedKeys(schema, null,...) //tablename = null
while (rs.next()){...}

It now performs
---------------
ResultSet tables = getTables(schema,...);
while (tables.next()){
  rs = getExportedKeys(schema, tables.getString("TABLE_NAME"), ...)
  while (rs.next()){...}
}

This is in compliance with the JDBC API. allsuites runs without failures/errors. derbyall
not run because only junit test code is modified. 

> junit tests uses getExportedKeys with table name null
> -----------------------------------------------------
>
>                 Key: DERBY-2595
>                 URL: https://issues.apache.org/jira/browse/DERBY-2595
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.2.0
>            Reporter: Jørgen Løland
>         Assigned To: Jørgen Løland
>         Attachments: DERBY-2595-1.diff, DERBY-2595-1.stat
>
>
> org.apache.derbyTesting.junit.JDBC.dropSchema uses DatabaseMetadata#getExportedKeys with
null as table name. This is not allowed according to java.sql.DatabaseMetaData. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message