Subject | Re: [Firebird-Architect] FB 2.0 Road Map |
---|---|
Author | Jim Starkey |
Post date | 2004-09-09T15:00:29Z |
Alexandre Benson Smith wrote:
true if the two operands were equivalent -- either equal in value or
both missing. This would avoid a special case in a trigger while making
a useful construct available in all contexts. I'd be surprised if some
other database systems didn't already have such an operator; if so, we
should consider their choice of operator. If I were a less cynical
person, I'd suggest "==".
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>Hi !A more general solution would be a comparison operator that returned
>
>I have read th FB 2.0 RoadMap, and wish to ask for a feature request.
>
>I have discussed this on firebird-support some time ago.
>
>What I think could be implemented in FB is a UPDATED function that will
>run insed triggers, this function will be used to test if a column was
>modified.
>
>In triggers I use to do this
>
>If (
> (Old.Quantity <> New.Quantity) or
> ((Old.Quantity is null) and (New.Quantity is not null)) or
> ((Old.Quantity is not null) and (New.Quantity is null))
> ) then
>
>This will be changed by
>
>if Updated(ColumnA) then
>
>in delete or insert triggers UPDATED always return true, and in update
>triggers should work as above.
>
>
>
true if the two operands were equivalent -- either equal in value or
both missing. This would avoid a special case in a trigger while making
a useful construct available in all contexts. I'd be surprised if some
other database systems didn't already have such an operator; if so, we
should consider their choice of operator. If I were a less cynical
person, I'd suggest "==".
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376