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
I think if NULL is allowed, it's better to replace by NULL, as every other date could interfere with the regularly stored dates and it seems to be the only value in postgres representing "undefined". Maybe an option should be used to let the user decide, what to do when the date is a NOT NULL column. This option could then default to 1971-01-01.
Problem: Having a MySQL date field with an undefined date
0000-00-00
, it will be the same value in the output. Resulting in:Solution: It should be
NULL
instead, because that seems to be the Postgres standard for an undefined date.The text was updated successfully, but these errors were encountered: