Rich Shepard <rshepard@appl-ecosys.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
