Re: Blank, nullable date column rejected by psql

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Blank, nullable date column rejected by psql
Date: 2019-02-12 13:42:56
Message-ID: alpine.LNX.2.20.1902120538510.15295@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 12 Feb 2019, Laurenz Albe wrote:

> If you insert a string into a "date" column, PostgreSQL will try to
> convert the string to a date with the type input function. The type input
> function fails on an empty string, since it cannot parse it into a valid
> "date" value. This also applies to the empty string.

Laurenz,

All my previous databases with date columns were required to have an entry
because each row contatined spatio-temporal sampling data. The table in this
business-oriented application is not required to have a next_contact date
and (the crucial point) is that I conflated date values with string values.
As you wrote, a date column is converted from the entered string to a
non-string date type and requires an explicit null when there is no value to
be stored for that column.

Thanks very much,

Rich

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-02-12 14:14:06 Re: SV: Implementing pgaudit extension on Microsoft Windows
Previous Message github kran 2019-02-12 13:07:54 Re: Aurora Postgresql RDS DB Latency