You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jørgen Løland (JIRA)" <ji...@apache.org> on 2007/05/04 09:11:18 UTC
[jira] Created: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
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
Fix For: 10.3.0.0
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.
[jira] Commented: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504191 ]
Thomas Nielsen commented on DERBY-2607:
---------------------------------------
Added checks for tablename==null and exception throwing for getExportedKeys and getImportedKeys to align the other methods.
derbyAll runs without failures or errors, while suites.All has 4 failures due to unrelated issue with encryption.
Maybe the extra ";" in getExportedKeysX should be removed as well when touching the file?
> 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
> Assignee: Thomas Nielsen
> 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.
[jira] Updated: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen updated DERBY-2607:
------------------------------------
Fix Version/s: 10.4.0.0
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Resolved: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen resolved DERBY-2607.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Merged from trunk: svn merge -r 548250:548251 https://svn.apache.org/repos/asf/db/derby/code/trunk
Committed revision 548252 on 10.3
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.0.0, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Closed: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen closed DERBY-2607.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.3.1.1
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.0.0, 10.3.1.1, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Commented: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505721 ]
Bernt M. Johnsen commented on DERBY-2607:
-----------------------------------------
Committed revision 548251 on trunk.
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Updated: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland closed DERBY-2607.
--------------------------------
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.0.0, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Reopened: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nielsen reopened DERBY-2607:
-----------------------------------
Not supposed to be resolved until commited :)
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Attachments: d2607.diff
>
>
> 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.
[jira] Closed: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-2607.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 10.3.0.0)
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.1.1, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Updated: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nielsen updated DERBY-2607:
----------------------------------
Attachment: d2607.diff
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Attachments: d2607.diff
>
>
> 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.
[jira] Reopened: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reopened DERBY-2607:
---------------------------------------
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.1.1, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Assigned: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nielsen reassigned DERBY-2607:
-------------------------------------
Assignee: Thomas Nielsen
> 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
> Assignee: Thomas Nielsen
> 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.
[jira] Reopened: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen reopened DERBY-2607:
-------------------------------------
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Fix For: 10.3.0.0, 10.3.1.1, 10.4.0.0
>
> Attachments: d2607.diff
>
>
> 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.
[jira] Resolved: (DERBY-2607) DatabaseMetaData is not consistent
about throwing SqlException when tablename=null
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Nielsen resolved DERBY-2607.
-----------------------------------
Resolution: Fixed
Derby Info: [Patch Available]
> 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
> Assignee: Thomas Nielsen
> Priority: Trivial
> Attachments: d2607.diff
>
>
> 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.