[
https://issues.apache.org/jira/browse/OFBIZ-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600990#comment-14600990 ]
Gareth Carter commented on OFBIZ-5608:
--------------------------------------
I do not know if it does rounding - but it certainly seems to ignore the time when storing and normalizes the time to midnight on retrieval as per API. You just set the time to midnight in the converters which should happen anyway.
I don't believe there will be any data corruption if app servers have different timezones. If you use the system timezone on any instance to create a java.sql.Date from a string and store that java.sql.Date into the database using PreparedStatement.setDate(i, x) then the output of toString() will be what is stored in the database. Personally I believe most jdbc drivers work with the year/month/day values that the java.sql.Date represents in the system timezone rather than the millisecond value that is actually used
> Dates Displaying Incorrectly With Negative Offest Timezones.
> ------------------------------------------------------------
>
> Key: OFBIZ-5608
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5608> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk
> Reporter: Rupert Howell
> Priority: Minor
> Attachments: IgnoreTimeZone.patch, ObjectTypeTests.patch, dates.patch, dates_1589040.patch, sqldate_scenarios.png
>
>
> Dates are displaying incorrectly when negative offset (relative to UTC) are applied by the users settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
