Hi Tom,
> Hi Michael,
>
> I am sure handling other data types with the more specific API would
> not hurt. The motivation for doing that would be if the more general
> API was causing some kind of problem.
>
> I have not heard of such a problem. Can you think of one?
I have not heard either. I just looked at the fix and was wondering
whether the problem with the Seoul timezone only occurred with a
java.sql.Date instance. The fix calls the specific API for instances of
type java.sql.Date and still uses statement.setObject(...) for
java.sql.Timestamp. I'm fine with this, if there is no problem. I'm just
asking :-).
Regards Michael
>
> -Tom
>
> Michael Bouschen wrote:
>
>> Hi,
>>
>> The fix for issue 1878 (date query test issues when running in the
>> Seoul timezone:
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=1878)
>> introduced some special handling for java.sql.Date instance into the
>> OraclePlatform. I was wondering whether we need to do a similar thing
>> for other date/time instances such as java.sql.Timestamp etc.
>>
>> Any idea? I haven't heard anything back from my previous question.
>>
>> Regards Michael
>>
>>
>>