[
https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494069
]
Daniel John Debrunner commented on DERBY-1484:
----------------------------------------------
The release note indicates that the new behaviour is correct, but doesn't it
still allow a pattern to be used, which does not conform to the standard?
> 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, 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Jørgen Løland
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1484-2.diff, DERBY-1484-2.stat, DERBY-1484-3.diff,
> DERBY-1484-3.stat, DERBY-1484.diff, DERBY-1484.stat, releaseNote.html
>
>
> 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.
