kiosk sync: a record that got modified by one dock and deleted by another is never dropped

[urapadmin]

coming out of #2931:

two docks A and B: A modified a record first, then B deletes it a bit later.
In synchronization the record does not get deleted.

I can't really see why.

[urapadmin]

Confirmed. The reason is that I have NO time stamp of the deletion. The time stamp of all deletions is the fork time of the dock PLUS arbitrary 2 seconds to make sure it is actually ahead of the main record.

The result is that a modification is ALWAYS ahead of that and will win.

I am actually not that unhappy with it because I think I'd rather keep a record in such a dubious case. I only take issue with the fact that this is a side effect rather than planned behaviour.

[urapadmin]

Koisk 1.6.6.4

• in such a case Kiosk will inform:

Synchronization._sync_deleted_records: X rows got deleted by at least one dock but REMAIN in table XYZ because
they were also modified by at least one dock. Kiosk resolves such peculiarities ALWAYS by keeping rather than losing data.

This is not really a time zone issue, it was exactly like that in older Kiosk versions as well. Can be tested with two devices in the same time zone, too.