Blank, nullable date column rejected by psql - Mailing list pgsql-general

From Rich Shepard
Subject Blank, nullable date column rejected by psql
Date
Msg-id alpine.LNX.2.20.1902111434330.28800@salmo.appl-ecosys.com
Whole thread Raw
Responses Re: Blank, nullable date column rejected by psql  (Ron <ronljohnsonjr@gmail.com>)
Re: Blank, nullable date column rejected by psql  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Blank, nullable date column rejected by psql  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Blank, nullable date column rejected by psql  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: Blank, nullable date column rejected by psql  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
Running postgresql-10.5 on Slackware-14.2.

A table has a column defined as

Column       | Type  | Collation | Nullable | Default
next_contact | date  |           |          |

In a .sql file to insert rows in this table psql has a problem when there's
no value for the next_contact column:

$ psql -f activities.sql -d bustrac 
psql:activities.sql:6: ERROR:  invalid input syntax for type date: ""
LINE 2: ...ise. Asked him to call.',''),

Explicitly replacing the blank field ('') with null is accepted. Why is
this?

Now I know to replace no dates with null I'll do so but I'm curious why this
is needed.

Thanks in advance,

Rich



pgsql-general by date:

Previous
From: Michael Lewis
Date:
Subject: Re: Aurora Postgresql RDS DB Latency
Next
From: Ron
Date:
Subject: Re: Blank, nullable date column rejected by psql