> there might be a bug in the replace-conflict handler of sqlite-2.8.15...

What you are seeing is the correct behavior; the entire row
is replaced.  Perhaps you are confusing insert with update.

Regards

Reply via email to