View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004610 | SymmetricDS | Bug | public | 2020-10-29 16:13 | 2020-11-09 15:15 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.12.4 | ||||
| Target Version | 3.12.5 | Fixed in Version | 3.12.5 | ||
| Summary | 0004610: Postgres Conflict Resolution fails to resolve | ||||
| Description | Postgres Conflict Resolution fails to resolve primary key constraint, unique index constraint, and foreign key constraint errors. The integration tests are failing, and customers have reported the same thing. | ||||
| Steps To Reproduce | Run the integration tests for Postgres. | ||||
| Additional Information | Because of the functionality that adds "on conflict do nothing" to the insert statements, the knowledge of what type of constraint error is lost. When the insert returns 0 rows inserted, we need to insert the same statement without the "on conflict do nothing" clause on a different connection and catch the exception so that we can notify the caller what type of conflict error occurred. | ||||
| Tags | dialect: postgresql | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-10-29 16:13 | pmarzullo | New Issue | |
| 2020-10-29 16:13 | pmarzullo | Status | new => assigned |
| 2020-10-29 16:13 | pmarzullo | Assigned To | => pmarzullo |
| 2020-10-29 16:13 | pmarzullo | Tag Attached: dialect: postgresql | |
| 2020-10-29 16:13 | pmarzullo | Relationship added | related to 0004609 |
| 2020-10-29 17:02 | pmarzullo | Status | assigned => resolved |
| 2020-10-29 17:02 | pmarzullo | Resolution | open => fixed |
| 2020-10-29 17:02 | pmarzullo | Fixed in Version | => 3.12.5 |
| 2020-11-09 15:15 | admin | Status | resolved => closed |