Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 8 May 2012 04:13:22 +0000 (UTC)
From: "Jayaram Subramanian (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <812527447.37423.1336450402153.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-4633) Cache default calendar in result sets
 and statements on client driver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jayaram Subramanian updated DERBY-4633:
---------------------------------------

    Attachment: Main.java

Attached is the test java program
                
> 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
>         Attachments: Main.java
>
>
> 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