You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/05/18 06:10:16 UTC

[jira] Resolved: (DERBY-1985) Use Calendar.setTimeInMillis(long) instead of Calendar.setTime(Date) for performance.

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

Daniel John Debrunner resolved DERBY-1985.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

Believe all uses of Calendar.getTime()/setTime() that could be more efficient by using the millisecond version have been addressed.

> Use Calendar.setTimeInMillis(long) instead of Calendar.setTime(Date) for performance.
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-1985
>                 URL: https://issues.apache.org/jira/browse/DERBY-1985
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.3.0.0
>
>
> Calendar.setTimeInMillis(long) could not be used with JDK 1.3 as the method existed but was protected, it became public in JDK 1.4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.