[pgjdbc/pgjdbc] 1ca0c5: fix: support insert ... on conflict...updatefor r... - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject [pgjdbc/pgjdbc] 1ca0c5: fix: support insert ... on conflict...updatefor r...
Date
Msg-id 5aa13571c92ff_79672adebbe83c0c32939@hookshot-fe-88eb02d.cp1-iad.github.net.mail
Whole thread Raw
List pgsql-jdbc
Branch: refs/heads/master
  Home:   https://github.com/pgjdbc/pgjdbc
  Commit: 1ca0c5864a8b6c575b32aee03e2e1e8848fee143
      https://github.com/pgjdbc/pgjdbc/commit/1ca0c5864a8b6c575b32aee03e2e1e8848fee143
  Author: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
  Date:   2018-03-08 (Thu, 08 Mar 2018)

  Changed paths:
    M CHANGELOG.md
    M pgjdbc/src/main/java/org/postgresql/core/Parser.java
    M pgjdbc/src/test/java/org/postgresql/core/ParserTest.java
    M pgjdbc/src/test/java/org/postgresql/test/jdbc2/UpsertTest.java

  Log Message:
  -----------
  fix: support insert ... on conflict...update for reWriteBatchedInserts=true (#1130)

pgjdbc will avoid rewriting the query if a bind is identified after values(...)

That is ON CONFLICT... DO update set x=? is NOT rewrite-compatible, and update set x='default' is rewrite-compatible

"reported" here:
https://stackoverflow.com/questions/47664889/jdbc-batch-operations-understanding/48349524?noredirect=1#comment84691562_48349524



pgsql-jdbc by date:

Previous
From: Christopher BROWN
Date:
Subject: Re: Handling transaction failure due to concurrency errors
Next
From: Vladimir Sitnikov
Date:
Subject: [pgjdbc/pgjdbc] af64ed: fix: allowEncodingChanges should allow setclient_...