-
-
Couldn't load subscription status.
- Fork 252
Open
Labels
s: triageSome tests need to be run to confirm the issueSome tests need to be run to confirm the issue
Description
Description
I have upgraded from buffalo 16.5 to buffalo 16.15 and it seems that some module (I assume buffalo-pop) has some breaking changes. I am using postgres to store timestamp with timezone values. Postgres contains values with 0 timezone (+00), however, when I read the value with buffalo, the value gets my timezone (+3) appended to the value. This only started to happen when I did the buffalo 16.15 upgrade. It seems like a bug to me
Steps to Reproduce the Problem
- Store a timestamp with a zero timezone in postgres
- Read the struct using pop model load (your system time should be in other than the +0 timezone )
For me, this has happened while executing a test, which works fine with older pop and fizz versions
Expected Behavior
I am expecting the timezone to be the same as in the database.
Actual Behavior
The local timezone of the OS seems to be appended to the resulting value
Info
MacOS X Mojave, Pop version 16.15, used through Buffalo
Metadata
Metadata
Assignees
Labels
s: triageSome tests need to be run to confirm the issueSome tests need to be run to confirm the issue