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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2014/06/25 19:54:24 UTC

[jira] [Updated] (DERBY-6638) Remove unnecessary use of reflection in SignatureChecker

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

Dag H. Wanvik updated DERBY-6638:
---------------------------------

    Attachment: derby-6638.status
                derby-6638.diff

Attaching a patch to remove the reflection + some missing javadocs and IDE warning fixes. I tested the tool manually for a simple case, but see DERBY-6639.

> Remove unnecessary use of reflection in SignatureChecker
> --------------------------------------------------------
>
>                 Key: DERBY-6638
>                 URL: https://issues.apache.org/jira/browse/DERBY-6638
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Dag H. Wanvik
>         Attachments: derby-6638.diff, derby-6638.status
>
>
> Ca line 377 in SignatureChecker we use reflection to call DatabaseMetaData#getFunctionColumns. This is no longer necessary after we removed support for JDR 169.



--
This message was sent by Atlassian JIRA
(v6.2#6252)