Re: QUE: What was the reason for IF NOT( A IS NOT NULL) THEN

From: <czetie_at_nospam.us.oracle.com>
Date: 1998/03/17
Message-ID: <350EE904.7AC3_at_nospam.us.oracle.com>#1/1


Dieze Informatisering B.V. wrote:
>
> I am sorry but my neurons are failing me. I know I had someone explain
> it to me before and it sounded so simple and logical then, that I did
> not make a note of it.
>
> Can Someone Please explain me again The reason for statements like
>
> IF NOT( A IS NOT NULL) THEN ...
>
> in e.g. the when-validate-item triggers in Forms 4.5 default blocks?
>
> Was it because:
> A. The field A has a constraint defined forcing it not to be NULL
> and so the when validate field trigger gets a statement generated
> forcing to check whether the condition is fulfilled: hence if NOT
> <condition> THEN
>
> OR was it
> B. The contruction NOT (A IS NOT NULL) simply evaluates quickest
> and even the extra NOT operator cannot undo the timegain when
> evaluating A IS NOT NULL (in comparison to A IS NULL of course).
>

Option A. The code is, as you deduce, simply IF NOT (constraint) THEN Received on Tue Mar 17 1998 - 00:00:00 CET

Original text of this message