View Issue Details

IDProjectCategoryView StatusLast Update
0005675SymmetricDSImprovementpublic2023-02-08 18:00
Reportercquamme Assigned Tocquamme  
Prioritynormal 
Status closedResolutionfixed 
Target Version3.14.5Fixed in Version3.14.5 
Summary0005675: Bidirectional sync causes need for trigger to be re-built on target side if table does not exist
DescriptionIf you set up bi-directional sync for a table and the table does not exist on the target side, then the trigger will be broken (correctly). However, once you send an initial load with a create table to the target side, the table will then exist on the target side, so the trigger can be rebuilt successfully. Rather than have the user manually rebuild this trigger, we can resync the triggers after an initial load with a create, and this will rebuild the trigger automatically.
Steps To Reproduce1. Set up a postgres source and target node
2. Create a table on the source node that does not exist on the target node
3. Use the add table wizard to create a bidirectional sync on the table between the source and target node
4. Trigger will be broken on the target side
5. Send an initial load with a create table from source to target
6. Trigger will still be broken on target side, but can be rebuilt now because the table exists on the target side
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.14 385f8e85

2023-01-31 20:44:20

cquamme

Details Diff
0005675: Bidirectional sync causes need for trigger to be re-built on
target side if table does not exist
Affected Issues
0005675
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/load/ConfigurationChangedDatabaseWriterFilter.java Diff File

SymmetricDS: 3.14 36291ed5

2023-02-08 17:37:24

admin

Details Diff
0005675: sync triggers was being called twice Affected Issues
0005675
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/load/ConfigurationChangedDatabaseWriterFilter.java Diff File

Issue History

Date Modified Username Field Change
2023-01-31 20:40 cquamme New Issue
2023-01-31 20:40 cquamme Status new => assigned
2023-01-31 20:40 cquamme Assigned To => cquamme
2023-01-31 20:44 cquamme Status assigned => resolved
2023-01-31 20:44 cquamme Resolution open => fixed
2023-01-31 21:00 cquamme Changeset attached => SymmetricDS 3.14 385f8e85
2023-02-08 18:00 admin Changeset attached => SymmetricDS 3.14 36291ed5
2023-02-15 20:26 admin Status resolved => closed