Great question and you're not doing anything wrong! I was stumped on this as well a while back.
Hereβs whatβs happening:
Youβre using the PostgreSQL data type timestamp without time zone. That means your DB column does not store any timezone information.
But Why Does It Show in UTC in Retool?
Because Retool's query engine and UI automatically formats timestamps using UTC by default. Even when the DB column itself is timezone-less, Retool assumes UTC when displaying timestamp values.
No actual timezone conversion is occurring on the DB side β it's a display-side behavior only in Retool.
did you find a workaround that's not crazy hacky? or just lived with it?
I also don't see why Retool would decide to edit the display of what the DB returns!! If I chose it to be without timezone, there's a reason I did that.
Haha, yes, that stumped me for a while so I can relate!
What you are looking at is just a sample of the data. When you display it in the app you can use any format you like. Are you going to display it in a table? Send me a screenshot of a component and I can help.
In my query, you see the timezone (display-side behavior only in Retool).
However, when you add the data in a table, you automatically see your correct data without the timezone.