- My goal: store time in UTC, display time in local TZ
- Issue: the datetime.value.unixTimestamp is in local TZ regardless of "Value" setting set to Local or UTC
- Additional info:
wait
1 Like
no, wait.
I have a data source which has 1752334885 as a timestamp.
It corresponds to:
% date -z UTC -r 1752334885
Sat Jul 12 15:41:25 UTC 2025
but this setting of a table column gives me time in my timezone, not UTC.
which is precisely my local timezone:
% date -r 1752334885
Sat Jul 12 19:41:25 +04 2025
How does that make sense?
I'm also curious to know how times are read and recorded.
I'm in an interesting situation with daylight savings that is causing data to be dropped in my database by Retool at 1AM.
It's meant to drop any records from the same day, with the expectation that the last records of the day survive after midnight as a snapshot.
Hi @pavelgur,
Got a little confused on this one 
I thought it might have been related to changes we made to the moment.js import that was causing some time related issues for other users.
For the table to display the UTC time, you may need to format the incoming data that is the source differently. The +04 in the date snippet you provided is telling the code to offset UTC by 4 hours, which is potentially why it is displaying your local time.
Apologies for the issue @ferret141,
Day light savings has been a nemesis of software for a while now, hopefully we can get rid of it so no one has to change their clocks or code
I believe we don't have any native solutions for this and the work around would be to manually move the time for your automated dropping of records by one our now and then change this again when daylights saving occurs 