Content-Type: text/plain;
  charset="iso-8859-1"
From: sad <sad@bankir.ru>
Organization: IT
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Subject: Re: feature request ?
Date: Thu, 24 Jun 2004 17:24:14 +0400
User-Agent: KMail/1.4.3
Cc: "Gregory S. Williamson" <gsw@globexplorer.com>,
	pgsql-sql@postgresql.org
References: 
 <71E37EF6B7DCC1499CEA0316A256832801057B7C@loki.wc.globexplorer.net>
	<200406241655.26065.sad@bankir.ru>
	<20040624065015.Y87012@megazone.bigpanda.com>
In-Reply-To: <20040624065015.Y87012@megazone.bigpanda.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200406241724.14810.sad@bankir.ru>

>  then lots of currently perfectly correct
> programs break.  If they're the same, then ELSE has different meanings
> depending on whether NULL is specified, and that's generally bad from an
> understanding the language standpoint.

i've already thougth on this
new control structure needed
but the name of the IF is perfect %-)

> In addition, either adding a FALSE and NULL or just a NULL still involves
> looking at the rest of the IF semantics to make sure they make sense.  How
> do those interact with ELSIF blocks?

that is because we used to two-valued BOOL...=20
but anyway i see no clear way to generalize ELSEIF.

may i suppose it was wrong to historically define IF as two-blocks control =
in=20
plpgsql ?
forget it.