[jira] [Updated] (DERBY-2139) executing getXXX() for a column checks the column position is in range three times, reduce to one.

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

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

Mamta A. Satoor updated DERBY-2139:
-----------------------------------

    Urgency: Low
     Labels: derby_triage10_11  (was: )
    
> executing getXXX() for a column checks the column position is in range three times, reduce to one.
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2139
>                 URL: https://issues.apache.org/jira/browse/DERBY-2139
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, SQL
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: d2139_getXXX_draft.txt
>
>
> On a getXXX() method the column position is checked in:
> Once in EmbedResultSet.getColumn()
> Twice in ValueRow.getColumn()
>   - once using explict code
>   - once implicitly when accessing the DataValueDescriptor array
> Can reduce to once by solely relying on the array bounds checking. Then change the defined api to Row.getColumn to state that it throws IndexOutOfBoundsException for an invalid column. EmbedResultSet.getColumn() then can catch that exception and throw the required SQLException.
> Probably need similar changes on the setXXX() methods and other getXXX methods and need to see how Row.getColumn() is used within the language layer.
>    

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