View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005820 | SymmetricDS | New Feature | public | 2023-05-03 13:16 | 2023-05-03 16:00 |
| Reporter | cquamme | Assigned To | cquamme | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.12.0 | ||||
| Target Version | 3.12.23 | Fixed in Version | 3.12.23 | ||
| Summary | 0005820: System property to control use of "on conflict" on Postgres | ||||
| Description | Add system property that can be set to prevent usage of "on conflict do nothing" during inserts. To prevent the batch from rolling back, it uses "on conflict do nothing" and checks if 0 rows were insert to detect a conflict. Instead, when postgres.use.on.conflict=false, it will use the older method of insert into table select where exists. Some users might need this if they use table partitioning based on inherits and a before trigger that causes 0 rows to be returned on all operations even when successfully -- they would also need to configure a conflict with a resolution of ignore. This was fixed in issue 0005341 and this issue is being created as a patch for 3.12.x versions. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-03 13:16 | cquamme | New Issue | |
| 2023-05-03 13:16 | cquamme | Status | new => assigned |
| 2023-05-03 13:16 | cquamme | Assigned To | => cquamme |
| 2023-05-03 13:17 | cquamme | Relationship added | related to 0005341 |
| 2023-05-03 13:19 | cquamme | Note Added: 0002311 | |
| 2023-05-03 15:11 | cquamme | Status | assigned => resolved |
| 2023-05-03 15:11 | cquamme | Resolution | open => fixed |
| 2023-05-03 15:11 | cquamme | Fixed in Version | => 3.12.23 |
| 2023-05-03 16:00 | cquamme | Changeset attached | => SymmetricDS 3.12 4b88e535 |
| 2023-05-12 19:43 | admin | Status | resolved => closed |