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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/05/15 09:16:16 UTC

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

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

Kristian Waagan resolved DERBY-2610.
------------------------------------

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Committed 'DERBY-2610-1.diff' to trunk with revision 538072.

Thanks for the patch!

> 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.