db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Closed: (DERBY-2610) Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns
Date Tue, 05 Jun 2007 09:34:26 GMT

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

Jørgen Løland closed DERBY-2610.
--------------------------------

    Resolution: Fixed
    Derby Info: [Existing Application Impact, Release Note Needed]  (was: [Existing Application
Impact])

> 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
>            Assignee: Jørgen Løland
>            Priority: Trivial
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-2610-1.diff, DERBY-2610-1.stat, releaseNote.html, releaseNote.html
>
>
> 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.


Mime
View raw message