Timezone within table data is changing when System date and Timezone is changed

[pturmel]

@utekarpranit02

No the DB is not preserving timezone information just the time
these are some sample dates stored

Correct, timestamptz doesn't save the inserted timezone. It always saves UTC timestamp for whatever was inserted. On SELECT, It always delivers that same "point in time" in whatever timezone the requestor is using. In JDBC, that delivers a java.util.Date (or java.sql.Timestamp, a subclass) at that UTC point in time, which then stringifies to whatever timezone the JVM is using.

@utekarpranit02

when system timezone is changed it is changing the timezone always.

No, the Ignition date object doesn't have a timezone. It carries UTC always. That object is stringified in whatever timezone is present when printed, logged, or deliberately formatted. Changing the system timezone changes the zone used for default stringification. Your DB data is correct. Your display/print/formatting operations are broken--don't use default stringification.

Please read this entire topic:

Ignition Perspective Page to show the client System date and time

Sure. I recommend DateTimeFormatter.ofPattern(). But I would move the complexity to a project script module with a DateTimeFormatter instance with your preferred pattern saved as a top level variable. Like so, perhaps: from java.time import ZoneId from java.time.format import DateTimeFormatter defaultFormatter = DateTimeFormatter.ofPattern("YYYY-MM-dd HH:mm") def zonedFormat(ts, zoneid, format=None): formatter = defaultFormatter if format is None else DateTimeFormatter.ofPattern(format) r…