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
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
When having a LocalDateTime with a negative year, this is encoded as a date string with a negative year (sign in front of the year number). But this throws an SQL-Error ErrorMessage(fields=Map(Line -> 3793, File -> datetime.c, SQLSTATE -> 22009, Routine -> DateTimeParseError, V -> ERROR, Message -> time zone displacement out of range: "-4713-01-01 00:53:28.000000", Severity -> ERROR)).
For postgres, negative years need to be encoded with a BC postfix after date string instead.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When having a LocalDateTime with a negative year, this is encoded as a date string with a negative year (sign in front of the year number). But this throws an SQL-Error
ErrorMessage(fields=Map(Line -> 3793, File -> datetime.c, SQLSTATE -> 22009, Routine -> DateTimeParseError, V -> ERROR, Message -> time zone displacement out of range: "-4713-01-01 00:53:28.000000", Severity -> ERROR))
.For postgres, negative years need to be encoded with a
BC
postfix after date string instead.The text was updated successfully, but these errors were encountered: