sandynz opened a new issue #14091:
URL: https://github.com/apache/shardingsphere/issues/14091
## Bug Report
### Which version of ShardingSphere did you use?
master branch
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
Updated record should be migrated to target database.
### Reason analyze (If you can)
In `PostgreSQLScalingSQLBuilder.buildConflictSQL`, `ON CONFLICT` it `DO
NOTHING`
```
private String buildConflictSQL(final DataRecord dataRecord) {
StringBuilder result = new StringBuilder(" ON CONFLICT (");
for (Column each : RecordUtil.extractPrimaryColumns(dataRecord)) {
result.append(each.getName()).append(",");
}
result.setLength(result.length() - 1);
result.append(") DO NOTHING");
return result.toString();
}
```
It seems cause issue, verification is needed for now.
`MySQLScalingSQLBuilder.buildDuplicateUpdateSQL` works.
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
### Example codes for reproduce this issue (such as a github link).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
