db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6063) Access static variables by class name in TabInfoImpl, InsertResultSet and ControlRow
Date Fri, 01 Feb 2013 07:05:13 GMT

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

Kristian Waagan updated DERBY-6063:
-----------------------------------

    Attachment: derby-6063-1a-statics_by_class_and_unused_method.diff

Attaching patch 1a.
The patch changes the access for static variables from instances to class names in three Derby
classes, removes an unused method in ControlRow, and removes some unused local variables I
spotted when browsing these three classes.

Patch ready for review.
                
> Access static variables by class name in TabInfoImpl, InsertResultSet and ControlRow
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-6063
>                 URL: https://issues.apache.org/jira/browse/DERBY-6063
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Store
>    Affects Versions: 10.10.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Trivial
>         Attachments: derby-6063-1a-statics_by_class_and_unused_method.diff
>
>
> Accessing static variables via an instance is causing trouble for a static code analysis
application. Since this way of accessing static variables is not recommended, I'm changing
the code to access the static variables via class names.
> I'm also removing an unused method in access/bree/ControlRow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message