From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Multi-row insert: error at terminal row. [RESOLVED] |
Date: | 2020-10-29 17:42:09 |
Message-ID: | 1589574.1603993329@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rich Shepard <rshepard(at)appl-ecosys(dot)com> writes:
> Found the problem in line 26 of 1925 rows: a non-null column had 'null'
> entered rather than one of the allowed values. That row was in the original
> database and I've no idea when I might have changed that.
> Why postgres didn't highlight that until I had only a 50-line .sql file I
> don't know. But, when bifircating the original file into smaller pieces and
> I got down to 50 lines postgres showed me exactly what the error was:
> psql:orgs-1.sql:50: ERROR: null value in column "industry" violates
> not-null constraint.
> Does this happen in newer versions than the 12.2 installed here?
That seems a bit odd. You're doing this in psql? Can you show
an exact example where the error report goes missing?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-10-29 17:45:05 | Re: Multi-row insert: error at terminal row. [RESOLVED] |
Previous Message | Rich Shepard | 2020-10-29 17:39:01 | Re: Multi-row insert: error at terminal row. [RESOLVED] |