View Issue Details

IDProjectCategoryView StatusLast Update
0006313SymmetricDSBugpublic2024-03-21 19:00
Reporterelong Assigned Toelong  
Prioritynormal 
Status resolvedResolutionfixed 
Product Version3.15.0 
Target Version3.15.5Fixed in Version3.15.5 
Summary0006313: Sync triggers for table should treat null or blank catalog/schema as default catalog/schema
DescriptionWhen 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.
Tagssync-trigger

Activities

There are no notes attached to this issue.

Issue History

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