"Plugge, Joe R." writes:
> This is what I have and it seems to work:
> IF OLD.password != NEW.password
It'd be better to write "IF OLD.password IS DISTINCT FROM NEW.password".
The way with != will not do what you want if one value is null and the
other isn't. It's possible this does
: Re: [SQL] Column Specific Update Trigger Routine
On 5/6/2010 4:12 PM, Plugge, Joe R. wrote:
I am trying to create a update trigger on a table that basically will only fire
when a specific column is updated. I am using version 8.4.3.
My plan of attack was to always fire on any row update, and
On 5/6/2010 4:12 PM, Plugge, Joe R. wrote:
>
> I am trying to create a update trigger on a table that basically will
> only fire when a specific column is updated. I am using version 8.4.3.
>
> My plan of attack was to always fire on any row update, and pass in
> the OLD and NEW column that I wa
Nevermind all, I figured it out
Thanks Dmitriy ...
From: Dmitriy Igrishin [mailto:dmit...@gmail.com]
Sent: Thursday, May 06, 2010 3:25 PM
To: Plugge, Joe R.
Subject: Re: [SQL] Column Specific Update Trigger Routine
Hey Plugge,
You dont need to pass OLD.* or NEW.* to the trigger function
I am trying to create a update trigger on a table that basically will only fire
when a specific column is updated. I am using version 8.4.3.
My plan of attack was to always fire on any row update, and pass in the OLD and
NEW column that I want to check.
CREATE TRIGGER check_lockout
AFTER U
