[
https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-1484:
---------------------------------
Attachment: DERBY-1484-3.stat
DERBY-1484-3.diff
The attached patch (3) includes all the changes in (2), and modifies a few
harness tests that previously called getExportedKeys and getImportedKeys with
table = null.
Since only table == null triggers an exception, it is still possible to call
these methods with a tablepattern, e.g. table="?". I will create a new issue
for changing the internal query to not accept patterns.
Derbyall and allsuites run fine except the following (unrelated) fails:
allsuites fails two ProcedureInTriggerTests, but these have already been
discussed in DERBY-1585 and should not be related to the patch. derbyall fails
bootLock (as always here - maybe because of NFS?)
> 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
> Assigned To: Jørgen Løland
> Priority: Minor
> Attachments: DERBY-1484-2.diff, DERBY-1484-2.stat, DERBY-1484-3.diff,
> DERBY-1484-3.stat, DERBY-1484.diff, DERBY-1484.stat
>
>
> 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.
