View Issue Details

IDProjectCategoryView StatusLast Update
0005633SymmetricDS ProImprovementpublic2022-12-13 21:31
Reporteremiller Assigned Toemiller  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.13.0 
Target Version3.13.10Fixed in Version3.13.10 
Summary0005633: Ensure that SQL Server log miner always captures deletes in foreign key order
DescriptionCurrently, the SQL Server log miner does not always capture deletes in foreign key order. The deletes do not get captured in foreign key order when they happen within the same transaction. This can cause unnecessary FK conflicts on the target, which can be especially troublesome considering the SQL Server log miner cannot capture old_data.
TagsNo tags attached.

Relationships

related to 0005632 closedemiller Ensure that SQL Server log miner always captures deletes in foreign key order 
related to 0005634 closedemiller Ensure that SQL Server log miner always captures deletes in foreign key order 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2022-12-13 18:46 emiller New Issue
2022-12-13 18:46 emiller Status new => assigned
2022-12-13 18:46 emiller Assigned To => emiller
2022-12-13 18:46 emiller Issue generated from: 0005632
2022-12-13 18:46 emiller Relationship added related to 0005632
2022-12-13 18:47 emiller Issue cloned: 0005634
2022-12-13 18:47 emiller Relationship added related to 0005634
2022-12-13 21:31 emiller Status assigned => resolved
2022-12-13 21:31 emiller Resolution open => fixed
2022-12-13 21:31 emiller Fixed in Version => 3.13.10
2023-01-16 20:51 admin Status resolved => closed