[jira] Updated: (DERBY-2610) Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns

["Jørgen Løland (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jørgen Løland updated DERBY-2610:
---------------------------------

    Attachment: DERBY-2610-1.diff
                DERBY-2610-1.stat

Patch (1)  removes table-patterns from the queries used by the seven methods. Note that there is one exception to this: the foreign table name of getCrossReference is still a pattern because this query is used by getExportedKeys with a wildcard. Removal of this pattern requires a new query for getExportedKeys

> Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2610
>                 URL: https://issues.apache.org/jira/browse/DERBY-2610
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.2.0, 10.3.0.0
>            Reporter: Jørgen Løland
>         Assigned To: Jørgen Løland
>            Priority: Trivial
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-2610-1.diff, DERBY-2610-1.stat
>
>
> The DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys do not allow table name patterns. However, the SQL in metadata.properties implement these with "table like ?", thus allowing patterns. The SQL for these methods should be modified to "table=?".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.