Re: pl/pgsql and controling loops - Mailing list pgsql-general

From aklaver@comcast.net (Adrian Klaver)
Subject Re: pl/pgsql and controling loops
Date
Msg-id 032720081913.19231.47EBF1E8000D791600004B1F22007374789D0A900E04050E@comcast.net
Whole thread Raw
In response to pl/pgsql and controling loops  ("Alain Roger" <raf.news@gmail.com>)
Responses Re: pl/pgsql and controling loops  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
 -------------- Original message ----------------------
From: "Alain Roger" <raf.news@gmail.com>
> Hi,
>
> i've read several books extract about controlling loops in postgreSQL under
> pl/pgsql and there is something interesting.
>
> once to do a comparison they use :
>
> > IF (ret == 1) THEN ...
>
>
> once,
>
> > IF (ret = 1) THEN...
>

Both are correct.

>
> so are they both correct ?
> comming from .NET/C++ world, usually we use '==' or '!=', so i expect that
> correct ones are '==' and '<>'.
>
> moreover, when i check if the returned value "ret_email" from SELECT email
> INTO ret_email FROM tmp_newsletterreg WHERE tmp_usr_id = id_session;
> i want to check if it is empty or not, so i do IF(ret_email <> '' ) THEN...
> but it does not work... every time it enter in the loop, even if it is empty
> string.
>
> where is the problem ?

Are you sure ret_email is an empty string and not a NULL value. <> won't work on a NULL value. You will need to use IS
NULLor IS NOT NULL. 
>
> thx.
>
> --
> Alain
> ------------------------------------
> Windows XP SP2
> PostgreSQL 8.2.4 / MS SQL server 2005
> Apache 2.2.4
> PHP 5.2.4
> C# 2005-2008

--
Adrian Klaver
aklaver@comcast.net


pgsql-general by date:

Previous
From: "Alain Roger"
Date:
Subject: pl/pgsql and controling loops
Next
From: "Alain Roger"
Date:
Subject: dunction issue