Our current implementation works fine, I tested by changing the timezone on my laptop time zone to Eastern Daylight Time (New York).
In both instances the time zone from the server is correctly offset on the UI to match my altered timezone, when I use `
{code:java}
new Date(versions[i][3]).toTimeString(); `
{code}
??Avoid timestamp without time zone (aka timestamp) and time without time zone (aka time). These columns do not know the time zone of a value, so different apps can insert values in different zones no one would ever know.??
> This would not happen for us as currently only our database is generating the timestamp values. I think we should still change it though, as it is generally seen as best practice to use `with time zone`, and it will future proof the database in the case where we need to start inserting values from the client (for example, a custom date being set). I will proceed with the change.
https://justatheory.com/2012/04/postgres-use-timestamptz/ |
|
