From: | sad <sad(at)bankir(dot)ru> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: feature request ? |
Date: | 2004-06-24 12:55:26 |
Message-ID: | 200406241655.26065.sad@bankir.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> If you were to add a NULL block you'd have to deal with things
> like, if you only have a then and else, do you run the else on NULL or do
> you do nothing? If you do nothing, what if you want the null and else to
> be the same, do you add another way to specify that? If you do the else,
> then the else stops making sense since it's sometimes false and sometimes
> not true.
it is only syntax problem.
really we have more than one way to continue execution if one block is skipped
so your are free to define IF's behavior any way, particularly the way it is
defined now.
two-blocks IF is oviously enough to code ANY algorythm
but the three-blocks IF is more adequate to tri-valued BOOL
From | Date | Subject | |
---|---|---|---|
Next Message | sad | 2004-06-24 13:24:14 | Re: feature request ? |
Previous Message | Alexander M. Pravking | 2004-06-24 10:32:48 | Re: feature request ? |