Jorge Solórzano schrieb am 01.02.2017 um 16:11:
> The use case for this is?
>
> AFAICT this is a libpq functionality, and since the JDBC driver is not libpq based then it can't use that
functionality.
>
> And it doesn't looks to be that useful for JDBC users:
I think it would:
postgres> \set VERBOSITY verbose
postgres> insert into foobar (data) values ('x');
ERROR: 23502: null value in column "id" violates not-null constraint
DETAIL: Failing row contains (null, x).
SCHEMA NAME: public
TABLE NAME: foobar
COLUMN NAME: id
LOCATION: ExecConstraints, execMain.c:1732
postgres>
When you run such an insert via JDBC, you'd only have "null value in column "id" violates not-null constraint" in the
SQLException's message.
But for logging purposes (on the client) it would be interesting to get details about the table into which the insert
wasdone.
This would enable to show those details (e.g. the table that was affected) in tools like SQL Workbench
Vladimir pointed me into the right direction. Those details are already available through the Postgres JDBC driver.
