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 2013/02/01 12:44:12 UTC
[jira] [Resolved] (DERBY-6063) Access static variables by class
name in TabInfoImpl, InsertResultSet and ControlRow
[ https://issues.apache.org/jira/browse/DERBY-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-6063.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
suites.All completed without errors.
Committed patch 1a to trunk with revision 1441396.
Resolving issue.
> 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
> Fix For: 10.10.0.0
>
> 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