db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods
Date Fri, 07 Jul 2006 13:00:29 GMT
Client and embedded behave differently when the table name is null in DatabaseMetaData methods
----------------------------------------------------------------------------------------------

         Key: DERBY-1484
         URL: http://issues.apache.org/jira/browse/DERBY-1484
     Project: Derby
        Type: Bug

  Components: JDBC, Network Client  
    Versions: 10.2.0.0    
    Reporter: Knut Anders Hatlen
    Priority: Minor


When giving null as table name to getBestRowIdentifier, getColumnPrivileges, getIndexInfo,
getVersionColumns or getPrimaryKeys, the client driver fails with "SQLException: Table name
can not be null". Embedded uses null as a wildcard and does not fail. Embedded and client
should have the same behaviour.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message