Revision history [back]

click to hide/show revision 1
initial version

answered 2020-02-07 14:36:02 +0800

cor3000 gravatar image cor3000

ZK Team

can you provide which component you are using causing this issue? Also what information are you reading from your DB? GMT-3 is an offset-timezone unaware of any daylight savings.

So your code might just do the correct thing and your preferred timeZone is incorrectly set to an offset timezone, and should instead be a named timezone in the form of "America/Halifax" or similar (you forgot to mention your countries timezone).

Hard coding the offset is most likely wrong, even if your country doesn't have DST now, it might have had DST in the past or switch in the future. Causing trouble at past or future dates you are reading from your DB.

can you provide which component you are using causing this issue? Also what information are you reading from your DB? GMT-3 is an offset-timezone unaware of any daylight savings.

So your code might just do the correct thing and your preferred timeZone is incorrectly set to an offset timezone, and should instead be a named timezone in the form of "America/Halifax" or similar (you forgot to mention your countries country's timezone).

Hard coding the offset is most likely wrong, even if your country doesn't have DST now, it might have had DST in the past or switch in the future. Causing trouble at past or future dates you are reading from your DB.

Support Options
  • Email Support
  • Training
  • Consulting
  • Outsourcing
Learn More