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
So, apparently due to time zone craziness, Postgresql can return dates like "1816-01-01 00:01:04+00:34:08" which fromSQL rejects as invalid because the regex doesn't expect seconds in the time offset.
The text was updated successfully, but these errors were encountered:
Unfortunately sub-minute offsets are really not very well supported in Luxon for various reasons. Internally, offset is stored in minutes. There are some ways to get fractional minutes in there, because some browsers return fractional seconds from Date#getTimezoneOffset. However this is not ideal at all, because it's all floating point math and not very accurate.
The proper fix requires some big refactors in this area to support sub-minute offsets.
This is not really my immediate radar, because sub-minute offsets are something that only occurs in historical time zone crazyness.
In the mean time, you probably should pre-process the timestamp you get from SQL to remove the second-based offset.
So, apparently due to time zone craziness, Postgresql can return dates like "1816-01-01 00:01:04+00:34:08" which fromSQL rejects as invalid because the regex doesn't expect seconds in the time offset.
The text was updated successfully, but these errors were encountered: