fix: EXPOSED-718 Fix timestamp column not storing values in UTC time zone

[joc-a]

Description

Summary of the change: Fixed timestamp column not storing values in UTC time zone

Detailed description:

• Why:
  Instant is in UTC time zone, and the expected behaviour is that the timestamp column should store values in UTC time zone since it is without a user-specified time zone. Using the session or system time zone leads to unexpected behaviour like this.
• How:
  Created new formatters that use the UTC timezone and used these formatters for timestamp column type.
  In JavaInstantColumnType and KotlinInstantColumnType, I modified the notNullValueToDB function to return the formatted String for MySQL (excluding MariaDB) because there was an issue with MySQL 5 where it implicitly converted the value to the session time zone when storing it and lead to an unexpected behaviour when the value is retrieved.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues