Hello everyone. I found out that exposed library h...

# exposed

[Anatoly]

Hello everyone.
I found out that exposed library have for me strange behaviour it's save Instance object to timestamp column with system timezone.

Instance it's UTC timezone
Java Timestamp it's UTC timezone
PostgreSQL column with type Timestamp it's UTC timezone

But the time that is saved in database PostgreSQL saves in my default system time zone. Is it expected behaviour?

[Anatoly]

image.png,image.png

[Anatoly]

IMHO it's incorrect behaviour

For localdatetime it's ok
But for instance everything should be in UTC format

[Dominik Sandjaja]

That's the reason why we explicitly set UTC everywhere ... This behavior led to some wrong approach times of our trucks ...

[Anatoly]

Recently, I find out that if you have column type timpestamptz not timestamp - every thing save correctly 🤔

[Anatoly]

And i read a lot of differences of this column types and there total mess in PostgreSQL ))
But one of the contributer to PostgreSQL recommends to use only timestamptz i decided to change all my column types, while i can))

[Anatoly]

https://justatheory.com/2012/04/postgres-use-timestamptz/

[Jocelyne Abi Haidar]

Hi @Anatoly, thank you for raising this issue. I created an issue on YouTrack and will be looking into it.

[Morten Andersen]

Hi @Jocelyne Abi Haidar - we just upgraded from 0.58.0 to 0.59.0 and EXPOSED-718 seems to have broken timestamp support in MySQL 8 - reported our findings in EXPOSED-737

[Morten Andersen]

@Jocelyne Abi Haidar - I saw your PR fix 🙇 - thanks for working so fast on it