[DERBY-2607] DatabaseMetaData is not consistent about throwing SqlException when tablename=null

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4, 10.4.1.3
• Component/s: Network Client
• Assignee: Thomas Nielsen
• Reporter: Jorgen Loland
• Created: 04/May/07 07:10
• Updated: 29/Jun/09 13:13
• Resolved: 06/Jul/07 14:45

Description

According to java.sql.DatabaseMetaData, the following DatabaseMetaData methods should not allow tablename=null:

getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys. In the five former methods, SqlExceptions are thrown if tablename == null, but this check is not performed in the latter two.

The method calls eventually end up in EmbedDatabaseMetaData, which performs this check. Hence, an exception is thrown either way. If we want the exception to be thrown as early as possible, the two latter methods should do so as well. If not, the check should be removed from the former methods.