Hi,
We are running self-hosted NocoDB using docker compose.
We used same TZ, non UTC, for DB(PG), docker host and inside docker container with NocoDB.
But when we create new record in any table column created_at fills with UTC timezone.
Can we change this somehow?
Create Time, Last Modified Time we prefer to store in UTC. However, its ALWAYS shown in the user’s timezone while viewing it in browser. While retrieving via API, it will be again based in UTC. Since it has TZ information, your application can adjust based on it.
What is the issue its causing to you?
I tried it using latest NocoDB docker release with PG as root DB – with both DB timezone set to default (UTC) and modified DB timezone (Tokyo/Japan). In both of these instances, the displayed timezone for CreatedAt & UpdatedAt fields matched browser timezone
Node: v22.18.0
Arch: arm64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.264.4
Issue that you are noticing is likely to be outside scope of NocoDB.
