Hi Kyle, hi Wonseok,
a small question: the fix adds some special handling for java.sql.Date
instances. Do we need to do the same for instances of type
java.util.Date or java.sql.Timestamp?
Regards Michael
> Hi Kyle,
> I could confirm that this work well in my environment(Korea/Seoul TZ).
> Now I don't need to change my timezone to run test against Oracle, thanks!
>
> My one concern is a typo in the comment - country is not Koreal but
> Korea.
> I will correct the comment in the code if you don't mind.
>
> Thanks,
> -Wonseok
>
> On 12/30/07, *Kyle Chen* < xiaosong.chen_at_oracle.com
> <mailto:xiaosong.chen_at_oracle.com>> wrote:
>
> Issue Number: 1878
> Submitted By: Kyle Chen
> Obtained From: TopLink
> Reviewed by: TopLink Team
> Short Description: Fix the bug that the wrong date is entered into
> the oracle database when the timezone is Koreal Seoul. The bug is
> fixed by caculating the date with the default timezone, which is
> that of the virtual machine running the application.
> Test: Tested with entity-persistence-tests.
>
>
>
>