This behavior is clearly wrong. A 1 hour change in a timezone and people's birthdays are wrong! Postgres is storing the date fields as date fields. It is OFBiz that is applying the LOCAL timezone information to the date on line 977 of UtilDateTime.
On 1 April 2014 09:27, <adrian.c...@sandglass-software.com> wrote: > The date is stored as a java.sql.Timestamp - which is referenced to UTC. > The UTC-referenced date is converted to the user's time zone during > display. This is the intended behavior. > > -Adrian > > > Quoting Rupert Howell <ruperthow...@provolve.com>: > > There's a definite problem with the way the dates are displayed in OFBiz. >> If you enter a birthday with your local timezone set to UTC, then change >> the timezone to -12, the birthday changes to the previous day. This is >> clearly wrong and is really apparent if you have your Server Timezone set >> to GB. If the birthday is within BST (April - October) and you are in GMT >> (Nov - March) they all appear incorrectly and vice versa. >> >> Ultimately this is caused by line 977 UtilDateTime >> >> f.setTimeZone(tz); >> >> Can anyone think of a legitimate reason why a date would have a timezone >> applied? A date is a date. January 1st is January 1st no matter where in >> the world you are. I would have thought if you want a date to be timezone >> dependent you'd use a Timestamp. >> >> I could patch line 666 of ModelFormField but I think it would be better to >> actually change the UtilDateTime method.. >> -- >> Rupert Howell >> >> Provolve Ltd >> Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK >> >> t: 01730 267868 / m: 079 0968 5308 >> e: ruperthow...@provolve.com >> w: http://www.provolve.com >> >> > > > -- Rupert Howell Provolve Ltd Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK t: 01730 267868 / m: 079 0968 5308 e: ruperthow...@provolve.com w: http://www.provolve.com
