[DERBY-1484] Client and embedded behave differently when the table name is null in DatabaseMetaData methods

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: JDBC, Network Client
• Issue & fix info: Release Note Needed
• Assignee: Jorgen Loland
• Reporter: Knut Anders Hatlen
• Created: 07/Jul/06 19:58
• Updated: 02/May/13 02:29
• Resolved: 14/May/07 15:38

Description

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.

Issue Links

• is blocked by: DERBY-2222 'show indexes in SCHEMANAME' does not work with the client driver
• is blocked by: DERBY-2595 junit tests uses getExportedKeys with table name null
• is depended upon by: DERBY-2610 Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.