Kevin Grittner <kgrittn@ymail.com> wrote:
> Your BEFORE UPDATE trigger could leave the "synced" value in NEW
> alone if force_sync was false, and set "synced" to false
> otherwise. It could then set NEW.force_sync to false, to leave you
> ready for the next update.
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.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
