From: sad <sad@bankir.ru>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Gregory S. Williamson <gsw@globexplorer.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: feature request ?
Date: Thu, 24 Jun 2004 17:24:14 +0400
Message-ID: <200406241724.14810.sad@bankir.ru> (raw)
In-Reply-To: <20040624065015.Y87012@megazone.bigpanda.com>
References: <71E37EF6B7DCC1499CEA0316A256832801057B7C@loki.wc.globexplorer.net>
<200406241655.26065.sad@bankir.ru>
<20040624065015.Y87012@megazone.bigpanda.com>
> 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...
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
plpgsql ?
forget it.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sad@bankir.ru, sszabo@megazone.bigpanda.com, gsw@globexplorer.com
Subject: Re: feature request ?
In-Reply-To: <200406241724.14810.sad@bankir.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox