Re: Multi-row insert: error at terminal row. [RESOLVED]
От | Adrian Klaver |
---|---|
Тема | Re: Multi-row insert: error at terminal row. [RESOLVED] |
Дата | |
Msg-id | d49801bd-6fe1-129a-cae7-fce34b5de48f@aklaver.com обсуждение исходный текст |
Ответ на | Re: Multi-row insert: error at terminal row. [RESOLVED] (Rich Shepard <rshepard@appl-ecosys.com>) |
Ответы |
Re: Multi-row insert: error at terminal row. [RESOLVED]
|
Список | pgsql-general |
On 10/29/20 10:39 AM, Rich Shepard wrote: > On Thu, 29 Oct 2020, Rich Shepard wrote: > >> psql:organizations.sql:1926: ERROR: syntax error at or near ";" >> LINE 1925: ...m',null,'Port','Opportunity',null); > ^ >> I'm not seeing why that's an error. All previous rows terminate with a >> comma >> and I don't know where else to look for the reason. What am I missing >> seeing? > > Rob/Paul/David/Tom/Adrian: > > 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? Per Tom's response, I'm not sure how a constraint error got transformed into a syntax error? Is orgs-1.sql just the INSERT? How is that file being fed to psql? > > Whew! > > Stay well all ... and VOTE! > > Rich > > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: