You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2019. It is now read-only.
I found out that in the code here, the date field is being cast to timestamp. I have the timestamp inside the jsonb body with timezone. When I run this, the time zone is ignored and uses the one from the system, of course.
We should be using timestamptz here instead, right? After doing this change, it works as expected.
Let me know if this makes sense and I will create a PR with this small change.
The text was updated successfully, but these errors were encountered:
eduardomourar
changed the title
Problem with date with time zone within jsonb body
Timestamp with time zone issue in field of jsonb body
Mar 8, 2018
Yeah, a timestamp is appropriate for certain situations but I'm comfortable calling that a bug since almost everyone will expect a timestamptz. Go ahead and make the change (add a test too please!) and I'll cut 2.7.4.
Hello,
I am having an issue with massivejs v2.7.3 while running the following query:
I found out that in the code here, the date field is being cast to
timestamp
. I have the timestamp inside the jsonb body with timezone. When I run this, the time zone is ignored and uses the one from the system, of course.We should be using
timestamptz
here instead, right? After doing this change, it works as expected.Let me know if this makes sense and I will create a PR with this small change.
The text was updated successfully, but these errors were encountered: