db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1224) Remove unused variables in DatabaseMetaData
Date Mon, 29 Jun 2009 14:35:47 GMT

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

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

    Derby Categories: [Performance]

> Remove unused variables in DatabaseMetaData
> -------------------------------------------
>
>                 Key: DERBY-1224
>                 URL: https://issues.apache.org/jira/browse/DERBY-1224
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.2.1.6
>
>         Attachments: derby-1224-v1.diff, derby-1224-v1.stat
>
>
> org.apache.derby.client.am.DatabaseMetaData has a number of instance
> variables which don't seem to have any purpose:
>   lastGetColumnPrivilegesResultSet_
>   lastGetColumnsResultSet_
>   lastGetForeignKeysResultSet_
>   lastGetPrimaryKeysResultSet_
>   lastGetProcedureColumnsResultSet_
>   lastGetProceduresResultSet_
>   lastGetSpecialColumnsResultSet_
>   lastGetStatisticsResultSet_
>   lastGetTablePrivilegesResultSet_
>   lastGetTablesResultSet_
>   lastGetUDTsResultSet_
>   lastGetTypeInfoResultSet_
>   lastGetAttrResultSet_
>   lastGetSuperTypesResultSet_
>   lastGetSuperTablesResultSet_
> Each lastGetXXXResultSet_ variable is set when the corresponding
> getXXX method is invoked. However, the variables are never read, so
> they could just as well be removed. Removing them will reduce the
> memory footprint.

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