At 11:06 +0300 on 28/06/1999, Rudy Gireyev wrote:
> This may be slightly more reasonable. :-)
> But ideally one would like to say:
> SELECT * from chargehistory WHERE "new" is TRUE;
>
> No? :-)
If you are into semantics, I don't really think so. You say things like "If
unsure, ask an expert", n
On 28 Jun 99, at 9:24, Ansley, Michael wrote:
> >>> If I may add, I always found the practice of comparing boolean values
> to
> >>> "true" or to "false" rather funny. You take a boolean value, and
> compare it
> >>> to 'true'. You get a boolean result that is the same:
> >>>
> >>> Truth ta
>>> If I may add, I always found the practice of comparing boolean values
to
>>> "true" or to "false" rather funny. You take a boolean value, and
compare it
>>> to 'true'. You get a boolean result that is the same:
>>>
>>> Truth table of "new" = 't':
>>>
>>> newnew = true
>>>
At 16:24 +0300 on 24/06/1999, Michael J Davis wrote:
>
> select * from chargehistory where "new" = 't';
If I may add, I always found the practice of comparing boolean values to
"true" or to "false" rather funny. You take a boolean value, and compare it
to 'true'. You get a boolean result that i
select * from chargehistory where "new" = 't';
Boolean values are 't' and 'f'.
-Original Message-
From: Garry Dolley [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, June 24, 1999 7:01 AM
To: [EMAIL PROTECTED]
Subject:[ADMIN] how to use boo
