| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Clemens Eisserer <linuxhippy(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BEFORE UPDATE trigger doesn't change column value |
| Date: | 2013-04-06 14:49:03 |
| Message-ID: | 1365259743.76123.YahooMailNeo@web162903.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kevin Grittner <kgrittn(at)ymail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-04-06 16:03:54 | Re: Source code and database object identifiers |
| Previous Message | Kevin Grittner | 2013-04-06 13:52:06 | Re: BEFORE UPDATE trigger doesn't change column value |