Handling @db.Date fields client side from different Timezones (Postgres)
We have a database where some tables have date only fields (
When the server sends this data then javscript will create a
This causes the
We COULD simply say that all dates that we receive client side we add the current timezones offset so that it will then be correctly parsed as
So in short we do need some way to differenciate between how we parse
If we have the service for that entity client and server side then we could add a manual mapping client side to only parse the specific fields that we know are
I also don't want to resort to saving them as DateStrings since the Database shouldn't have to adjust (and lower) its capabilities because of the client and we would loose some possibilities that Dates can do which strings can't.
DateTime @db.DateWhen the server sends this data then javscript will create a
new Date()This causes the
@db.Date2025-04-20-4h2020-04-19T20.00.000ZWe COULD simply say that all dates that we receive client side we add the current timezones offset so that it will then be correctly parsed as
2020-04-20T00.00.000ZDateTimeSo in short we do need some way to differenciate between how we parse
DateTimedb.DateIf we have the service for that entity client and server side then we could add a manual mapping client side to only parse the specific fields that we know are
db.DateI also don't want to resort to saving them as DateStrings since the Database shouldn't have to adjust (and lower) its capabilities because of the client and we would loose some possibilities that Dates can do which strings can't.
