having issues with timezone
i have a simple defaultNow timestamp saving, but the db is giving the timestamp another hour behind?
eg. saving data at 17:00 in bst, should be 16:00 in utc, but the db is giving 15:00
18 Replies
Project ID:
3fad4fec-c497-4ecf-a107-dbd12bc4e0473fad4fec-c497-4ecf-a107-dbd12bc4e047
as per standard, the deployments operate on utc time
yeah im pretty baffled
these are the latest items being saved right now
which is -2, instead of -1
-2 from what? is that not a utc timestamp?
it seems to be an hour behind utc
utc right now is 16:40
but data is being saved at 15:40
have you somehow set a different timezone?
Where on the db?
Or in the data I’m saving?
ok interesting
this is on localhost - correct
this is deployed - incorrect
missing an hour
no clue what language this is, but instead of being ambiguous, specifically save the time as utc, then when reading the date back from the database convert to the desired time zone for display purposes only
my local nextjs code is showing the correct code, my deployed nextjs code is 1 hour behind
which is odd
specifically save the time as utcthat way no matter what timezone the computer / server uses, it will always be saved in a known timezone
seems to be some scheme defining language no clue
could you not just adjust with -1 hour
guys 🪤
doesnt that cheese look yummy brody