db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-2975) DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
Date Thu, 07 May 2009 16:19:30 GMT

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

Kathey Marsden reassigned DERBY-2975:
-------------------------------------

    Assignee:     (was: Abhilash T.G)

Unassigning due to inactivity.


> DRDAResultSet.setResultSet creates a new int array to hold type information on every
execution.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2975
>                 URL: https://issues.apache.org/jira/browse/DERBY-2975
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server, Newcomer, Performance
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> Tracing the code it seems that if a statement is prepared and executed multiple times
that new type information stored in DRDAResultSet is created and set every execution.
> This wastes cpu cycles as the type information can be determined once at prepare time
(I assume) and stored in DRDAPreparedStatement.
> It's a little unclear to me the code path for setting the type information, seems to
happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
> (but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me
of a Young Ones episode :-)

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