View Issue Details

IDProjectCategoryView StatusLast Update
0006530SymmetricDSBugpublic2024-07-15 20:00
Reporterpmarzullo Assigned Topmarzullo  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.14.15 
Target Version3.14.16Fixed in Version3.14.16 
Summary0006530: Conflict resolution needs to set source node ID when executing conflict resolution for a SQL Server log mining node
DescriptionWhen conflict resolution is executed for a node that is set up to use SQL Server log mining, it needs to set the source node ID for every DML statement so that the change will not be captured by the log miner and sent back to the source database.
Steps To Reproduce1. Set up SQL Server log mining for a source and target node
2. Set up 2 way synchronization
3. Execute following SQL statements on source and target
create table parent(id integer not null, constraint parent_pk primary key(id));
create table child(id integer not null, parentid integer not null, constraint child_pk primary key(id), foreign key (parentid) references parent(id));
4. Execute following SQL statements on source
alter table child nocheck constraint FK__child__parentid__351881F5; -- constraint name may be different
5. Set up bi-directional synchronization of parent and child
6. Execute following SQL statements on source, and make sure they are synched to target
insert into parent values(1);
insert into child values(1,1);
insert into child values(2,1);
7. Execute following SQL statement on source:
delete from parent where id=1;

No records will end up in the target database (for parent and child).
No records will end up in the source database (for parent and child).
The source should have maintained the child records.
Tagsdialect: sql-server, log miner

Activities

Related Changesets

SymmetricDS: 3.14 2eb2cd5c

2024-07-15 19:29:00

pmarzullo

Details Diff
0006530: Conflict resolution needs to set source node ID when executing
conflict resolution for a SQL Server log mining node
Affected Issues
0006530
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/DefaultDatabaseWriterConflictResolver.java Diff File

SymmetricDS: 3.15 4074f061

2024-07-15 19:29:00

pmarzullo

Details Diff
0006530: Conflict resolution needs to set source node ID when executing
conflict resolution for a SQL Server log mining node
Affected Issues
0006530
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/DefaultDatabaseWriterConflictResolver.java Diff File

Issue History

Date Modified Username Field Change
2024-07-15 19:23 pmarzullo New Issue
2024-07-15 19:23 pmarzullo Status new => assigned
2024-07-15 19:23 pmarzullo Assigned To => pmarzullo
2024-07-15 19:23 pmarzullo Tag Attached: dialect: sql-server
2024-07-15 19:23 pmarzullo Tag Attached: log miner
2024-07-15 19:41 pmarzullo Status assigned => resolved
2024-07-15 19:41 pmarzullo Resolution open => fixed
2024-07-15 19:41 pmarzullo Fixed in Version => 3.14.16
2024-07-15 19:41 pmarzullo Note Added: 0002477
2024-07-15 20:00 pmarzullo Changeset attached => SymmetricDS 3.14 2eb2cd5c
2024-07-15 20:00 pmarzullo Changeset attached => SymmetricDS 3.15 4074f061
2024-08-16 17:44 admin Status resolved => closed