Re: BEFORE UPDATE trigger doesn't change column value

[Clemens Eisserer <linuxhippy@xxxxxxxxx>]

Hi Kevin,

Sorry, that's the wrong way around.  I should have said:

Your BEFORE UPDATE trigger could leave the "synced" value in NEW

alone if force_sync was **true**, and set "synced" to false

otherwise.  It could then set NEW.force_sync to false, to leave you
ready for the next update.

Thanks for your advice (and the patience on this list in general).
Instead of using two columns, I now use an integer-column and set it to a value taken from an incrementing sequence.

Thanks again, Clemens