db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4633) Cache default calendar in result sets and statements on client driver
Date Tue, 21 Feb 2012 20:52:48 GMT

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

Kathey Marsden updated DERBY-4633:
----------------------------------

    Issue & fix info: Newcomer
             Urgency: Normal
              Labels: derby_triage10_9  (was: )

Triage for 10.9 
This might be an appropriate newcomer project with some guidance.

                
> Cache default calendar in result sets and statements on client driver
> ---------------------------------------------------------------------
>
>                 Key: DERBY-4633
>                 URL: https://issues.apache.org/jira/browse/DERBY-4633
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>    Affects Versions: 10.6.1.0
>            Reporter: Knut Anders Hatlen
>              Labels: derby_triage10_9
>
> After the changes in DERBY-4582, these methods now allocate a default calendar object
on each invocation (on the client driver), whereas they didn't before the fix:
> ResultSet.getDate(int)
> ResultSet.getTime(int)
> ResultSet.getTimestamp(int)
> PreparedStatement.setDate(int, java.sql.Date)
> PreparedStatement.setTime(int, java.sql.Time)
> PreparedStatement.setTimestamp(int, java.sql.Timestamp)
> CallableStatement.getDate(int)
> CallableStatement.getTime(int)
> CallableStatement.getTimestamp(int)
> The embedded driver prevents excessive allocation of default calendar objects in these
methods by caching an instance in ConnectionChild (the super-class of EmbedResultSet, EmbedPreparedStatement
and EmbedCallableStatement). We should do something similar on the client driver.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message