View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006271 | SymmetricDS | Bug | public | 2024-03-04 17:44 | 2024-04-19 15:46 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.0 | ||||
| Target Version | 3.15.4 | Fixed in Version | 3.15.4 | ||
| Summary | 0006271: Finding trigger histories should treat null or blank as default catalog/schema | ||||
| Description | The findTriggerHistories() routine of TriggerRouterService should treat a null or blank for catalog/schema as matching the default catalog/schema. There was a case where user setup table groups, but it couldn't find the trigger history. The Table object had catalog/schema filled in, but the trigger history had catalog/schema as null (because the table was in the default catalog/schema). This routine is called from other routines, like ones to send SQL events, schema events, file sync reload, and dbcompare. | ||||
| Tags | No tags attached. | ||||
|
SymmetricDS: 3.15 abe95758 2024-03-04 17:50:37 Details Diff |
0006271: Finding trigger histories should treat null or blank as default catalog/schema |
Affected Issues 0006271 |
|
| mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/TriggerRouterService.java | Diff File | ||
| mod - symmetric-core/src/test/java/org/jumpmind/symmetric/service/impl/TriggerRouterServiceTest.java | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-04 17:44 | elong | New Issue | |
| 2024-03-04 17:44 | elong | Status | new => assigned |
| 2024-03-04 17:44 | elong | Assigned To | => elong |
| 2024-03-04 17:50 | elong | Status | assigned => resolved |
| 2024-03-04 17:50 | elong | Resolution | open => fixed |
| 2024-03-04 17:50 | elong | Fixed in Version | => 3.15.4 |
| 2024-03-19 16:20 | admin | Status | resolved => closed |
| 2024-04-19 15:46 | admin | Changeset attached | => SymmetricDS 3.15 abe95758 |