View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006435 | SymmetricDS | Improvement | public | 2024-05-17 20:57 | 2024-05-17 21:00 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.0 | ||||
| Target Version | 3.15.7 | Fixed in Version | 3.15.7 | ||
| Summary | 0006435: Avoid checking newer capture time if table isn't being captured | ||||
| Description | When the conflict manger uses a resolver that picks the newer row, it checks for a newer capture time in the sym_data table. The default resolver is NEWER_WINS, even when using a load only node or when capture is only enabled for the source. In cases when the target table doesn't have capture enabled, the resolver doesn't need to look for a newer change, which saves overhead. | ||||
| Tags | conflict manager | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-05-17 20:57 | elong | New Issue | |
| 2024-05-17 20:57 | elong | Status | new => assigned |
| 2024-05-17 20:57 | elong | Assigned To | => elong |
| 2024-05-17 20:57 | elong | Tag Attached: conflict manager | |
| 2024-05-17 20:58 | elong | Status | assigned => resolved |
| 2024-05-17 20:58 | elong | Resolution | open => fixed |
| 2024-05-17 20:58 | elong | Fixed in Version | => 3.15.7 |
| 2024-05-17 21:00 | admin | Changeset attached | => SymmetricDS 3.15 8e3a3bf8 |
| 2024-06-07 16:46 | admin | Status | resolved => closed |