[jira] Commented: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

["Daniel John Debrunner (JIRA)" <ji...@apache.org>]

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

Daniel John Debrunner commented on DERBY-1484:
----------------------------------------------

The network client has the correct behaviour. the tableName parameters to these methods is not a pattern and is required to be an exact match to the stored table name, thus null is not allowed. This was discussed on the list in this thread:

http://mail-archives.apache.org/mod_mbox/db-derby-dev/200701.mbox/%3c45AD1A46.3060007@sun.com%3e

> Client and embedded behave differently when the table name is null in DatabaseMetaData methods
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1484
>                 URL: https://issues.apache.org/jira/browse/DERBY-1484
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.1.6
>            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.
-
You can reply to this email to add a comment to the issue online.