View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006313 | SymmetricDS | Bug | public | 2024-03-21 18:46 | 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.5 | Fixed in Version | 3.15.5 | ||
| Summary | 0006313: Sync triggers for table should treat null or blank catalog/schema as default catalog/schema | ||||
| Description | When syncing triggers for a specific table, the user can get a "table not found" because the comparison fails between a null or blank catalog/schema in the trigger history and a populated catalog/schema of the table. The following use cases are affected: - symadmin sync-triggers table_name - REST service call syncTriggersByTable - Manage -> Installed Triggers screen The performance is also slow because it is looking up the supporting trigger information for all triggers and tables, not just the one requested by the user. | ||||
| Tags | sync-trigger | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-21 18:46 | elong | New Issue | |
| 2024-03-21 18:46 | elong | Status | new => assigned |
| 2024-03-21 18:46 | elong | Assigned To | => elong |
| 2024-03-21 18:46 | elong | Tag Attached: sync-trigger | |
| 2024-03-21 19:00 | elong | Status | assigned => resolved |
| 2024-03-21 19:00 | elong | Resolution | open => fixed |
| 2024-03-21 19:00 | elong | Fixed in Version | => 3.15.5 |
| 2024-04-19 15:46 | admin | Changeset attached | => SymmetricDS 3.15 cf784e1f |
| 2024-04-23 16:58 | admin | Status | resolved => closed |