Why not "timestamp with timezone" for timestamp columns in database?

[emrahcom]

Is there any reason not to use timestamp with timezone for timestamp columns in database? I'm asking especially for postgres. As you can estimate, timestamp without timezone can cause confusion in some cases.

[aeneasr]

Timestamps are always UTC when stored in the database, iirc

[aeneasr]

Golang takes care of it though :) Do you have a concrete bug or reproducible issue?

[emrahcom]

In my current setup (v0.8.0-alpha.3) when I create a new account using browser flow, identities table stores the times using localtime (which is +03 in my postgresql server).

This is not a Docker setup. Kratos process and postgresql run on their own standalone server.

[emrahcom]

If you have a Dockerized Postgresql server, maybe it uses "Etc/UTC by default

[aeneasr]

I see, the PG driver we have and all the time tools we use assume UTC when no timezone is set. I'd recommend setting the schema or session timezone to UTC when using Ory Kratos. There's currently no better workaround unfortunately. The DBAL we use currently does not support creating timestampz.

[emrahcom]

Thank @aeneasr,

I decided to set 'Etc/UTC' as timezone for Kratos server and for Postgresql server. Also I have another custom table which has a 1-1 relation with Kratos's identities table. I added a timestamptz column in it, my app is using this column now