Collected from the PG bugs email list.
|Reported by||Dirkjan Ochtman|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 15666 Logged by: Dirkjan Ochtman Email address: (redacted) PostgreSQL version: 11.2 Operating system: Linux Description: I'm modifying the data model for the application I work on, and in the process of doing so, I'm seeing this error: db | 2019-03-04 09:48:54.485 UTC  ERROR: null value in column "accountid" violates not-null constraint db | 2019-03-04 09:48:54.485 UTC  DETAIL: Failing row contains (14, 138962.38, 0, null, 13). db | 2019-03-04 09:48:54.485 UTC  STATEMENT: insert into JournalEntryRecord (accountId, amount, journalEntryId, type, id) values ($1, $2, $3, $4, $5) This is very confusing to me because the tuple from the "Failing row" message clearly has the `null` in fourth position, but the error message reports that the column "accountid" (or "accountId" -- but I understand column names are casefolded) is the problem, which should ostensibly be the first value from the failing row tuple (if that tuple is ordered the same way as the statement suggests).
|2019-03-04 09:55:31+00||PG Bug reporting form||BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint|
|2019-03-04 14:27:43+00||Tom Lane||Re: BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint|
|2019-03-04 15:47:05+00||Dirkjan Ochtman||Re: BUG #15666: Seemingly incorrect error reporting/logging for violation of non-null constraint|