From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Blank, nullable date column rejected by psql |
Date: | 2019-02-11 22:49:50 |
Message-ID: | 814371b9-d223-239d-e138-5451a81af2d4@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/11/19 2:44 PM, Rich Shepard wrote:
> 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.
Because:
invalid input syntax for type date: ""
means you are trying to enter an empty string("") and that:
a) Is not NULL
b) Is not a valid date string.
>
> Thanks in advance,
>
> Rich
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-02-11 22:50:24 | Re: Blank, nullable date column rejected by psql |
Previous Message | Ron | 2019-02-11 22:49:34 | Re: Blank, nullable date column rejected by psql |