[
https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2607:
--------------------------------------
Fix Version/s: (was: 10.3.0.0)
Unsetting fix-in for 10.3. No changes have gone in yet, no patch is available,
no activity is shown...Should this issue still get address before/in 10.3 the
fix in can be set when the issue gets resolved.
> DatabaseMetaData is not consistent about throwing SqlException when
> tablename=null
> ----------------------------------------------------------------------------------
>
> Key: DERBY-2607
> URL: https://issues.apache.org/jira/browse/DERBY-2607
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Newcomer
> Affects Versions: 10.3.0.0
> Reporter: Jørgen Løland
> Priority: Trivial
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
