wstrzalka <[EMAIL PROTECTED]> writes:
> So - does it mean that the whole IF-ELSE-ENDIF is not parsed at once -
> but lazy-parsed when the control reaches it, while the IF condition is
> parsed as a single expression and therefore I get error in this case?
Right, for a suitable definition of "parse
On 23 Kwi, 16:32, [EMAIL PROTECTED] (Tom Lane) wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I think this business of non-shortcircuiting boolean operators is just
> > an artifact of the fact that PL/pgSQL hands off expression to the SQL
> > engine for evaluation.
>
> The complainant is n
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I think this business of non-shortcircuiting boolean operators is just
> an artifact of the fact that PL/pgSQL hands off expression to the SQL
> engine for evaluation.
The complainant is not actually complaining about non-shortcircuiting
boolean operato
Martijn van Oosterhout escribió:
> On Tue, Apr 22, 2008 at 02:41:50AM -0700, wstrzalka wrote:
> > One of the annoying things in plpgsql is logical expression
> > evaluation.
> >
> > In most (all??) languages I know, logical expression like:
> >
> > if ( [A_true_expression] or [B_false_expres
On Tue, Apr 22, 2008 at 02:41:50AM -0700, wstrzalka wrote:
> One of the annoying things in plpgsql is logical expression
> evaluation.
>
> In most (all??) languages I know, logical expression like:
>
> if ( [A_true_expression] or [B_false_expression] ) then
>
> will stop evaluating when the
