Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 04 Nov 2008 08:18:51 -0500
From: Lance Andersen <Lance.Andersen@Sun.COM>
Subject: Re: Date 2042-10-12 problem using Brasilia time zone
In-reply-to: <5f211bd50811040510o292df72cud9d7fb3a4f94c623@mail.gmail.com>
Sender: Lance.Andersen@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <97E95AFA-18C8-4705-9E48-7538B9BF92AB@sun.com>
MIME-version: 1.0
Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
References: <5f211bd50810310720l531b597fv3c4149e51eaf0a35@mail.gmail.com>
 <490B16B6.50107@optrak.co.uk> <20081031144518.GA2263@atum01.Norway.Sun.COM>
 <20081031144959.GB2263@atum01.Norway.Sun.COM>
 <5f211bd50810310814v7a5cd5ccgb4c0178631853593@mail.gmail.com>
 <x1oxy704b3yd.fsf@sun.com>
 <5f211bd50811030941n79569757n8ff8bb5ac991bc77@mail.gmail.com>
 <20081104082135.GA3250@atum01.Norway.Sun.COM>
 <2B9220EB-A07A-45CB-858C-C699ED127309@sun.com>
 <5f211bd50811040510o292df72cud9d7fb3a4f94c623@mail.gmail.com>


On Nov 4, 2008, at 8:10 AM, Thomas Mueller wrote:

> Hi,
>
>> this is *not* an issue with java.sql.Date.
>
> I am not sure about that.

java.sql.Date is nothing but a wrapper to java.util.Date, so what you  
pass in to the valueOf get passed directly to the constructor of  
java.util.Date(int,int, int).  All of the work is done in  
java.util.Date.


Regards
Lance
>
>
>> java.sql.Date.valueOf()  calls java.util.Date(int,int,int) and if  
>> you modify
>> your test program, you will see the same results from java.util.Date.
>
> I submitted the problem even without knowing the exact root cause. If
> you found the root cause of the problem, or if you even know how to
> fix it, that would be great of course!
>
> It looks like midnight of that day doesn't exist because it is the
> beginning or end of the daylight saving time. Where I live this change
> occurs at 2 am, but in some countries the change is at or near
> midnight. From what I know, java.util.Calendar doesn't allow to set
> 'invalid' hours, and if using the lenient setting it will 'fix' the
> time. Maybe the reason is that midnight of that day is set to 11 pm of
> the previous day. This change may be the expected behavior of
> java.util.Date / Calendar, but for java.sql.Date it is a problem. So
> maybe it is required to fix java.sql.Date, not java.util.Date. But I
> am not sure because I didn't debug it so far.
>
>> Please update any submitted bug
>
> I don't see a way to update the bug. I got a mail saying: "Your report
> has been assigned an internal review ID of 1384760, which is NOT
> visible on the Sun Developer Network (SDN)". There is no link.
>
> Regards,
> Thomas