[ https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland reassigned DERBY-1484: ------------------------------------ Assignee: Jørgen Løland > 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 > > 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.