Rows Inserts And Deleted Immediately

[peterlaursen]

we will certainly look into this Monday morning.

It would be a help is you attached a small dump with data to reproduce the porblem.

You can create a ticket if you do not want to expose the data in public.

[Santhosh]

peterlaursen wrote on Nov 18 2006, 09:11 PM:

we will certainly look into this Monday morning.

It would be a help is you attached a small dump with data to reproduce the porblem.

You can create a ticket if you do not want to expose the data in public.

Please get me the steps to create a ticket. I didn't find a place to raise ticket

[peterlaursen]

I think we found this issue now!

Problem is that there is a small time-slice between UPDATES and DELETES.  If there is activity in between and if for instance there is some counter in the table that counts how many times a topic has been opened, checksums will change in between.  Actually we have been able to reproduce with this Forum itself.

We will have to reuse the checksums, generate some snapshot of (parts of) the table or find some similar solution.

It may take some days to find and implement the optimal solution …

[peterlaursen]

Please try this:

http://www.webyog.com/downloads/betas/not_…QLyog523Ent.exe

With this build we have reversed the order or INSERTs, UPDATES and DELETES.

It will now perform those in the order DELETE -> INSERT -> UPDATE.

This will ensure that if some 'trigger code' in some application changes data (typically a 'counter' row) while the sync is running (between DELETEs and INSERTs) the target database will still have all rows existing on the source at the time the last checksum was collected.

It may display a log message like

Code:

DELETES INSERTS UPDATES
============================
37    42         7

.. in case that such 'trigger code' has been active (also if there actually was nothing to be deleted on target). Actually the rows affected will first be DELETEd on the target and next the updated row on source will be INSERTEd on target. So with this example this 'application trigger code' was active on 37 rows while the sync was running and 5 new rows and 7 updated rows were found.

[Author]

Posts