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
I've found an annoying bug while creating an app with [email protected]. I'm using PostgreSQL Database and have a table with a Timestamp field. Whenever a record is updated, the timestamp field adds one or two hours:
I have double checked that I am not touching that field, and I believe it has something to do with time zones and thus the difference of one or two hours being added (Daily Saving Time wether its summer or winter). The "timestamp" fields created_at and update_at however are working perfectly and on the database the fields are all of them timestamp with time zone, so I do not have any clue right now on how to fix it wether is a misconfiguration on my part or some bug on DenoDB.
Any help will be deeply appreciated!
The text was updated successfully, but these errors were encountered:
Hey there!
I've found an annoying bug while creating an app with [email protected]. I'm using PostgreSQL Database and have a table with a Timestamp field. Whenever a record is updated, the timestamp field adds one or two hours:
I have double checked that I am not touching that field, and I believe it has something to do with time zones and thus the difference of one or two hours being added (Daily Saving Time wether its summer or winter). The "timestamp" fields
created_at
andupdate_at
however are working perfectly and on the database the fields are all of themtimestamp with time zone
, so I do not have any clue right now on how to fix it wether is a misconfiguration on my part or some bug on DenoDB.Any help will be deeply appreciated!
The text was updated successfully, but these errors were encountered: