Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
10.2.1.6, 10.3.1.4
-
None
-
Release Note Needed
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.
Attachments
Attachments
Issue Links
- is blocked by
-
DERBY-2222 'show indexes in SCHEMANAME' does not work with the client driver
- Closed
-
DERBY-2595 junit tests uses getExportedKeys with table name null
- Closed
- is depended upon by
-
DERBY-2610 Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns
- Closed
- is part of
-
DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
- Closed