"Andrus" <[EMAIL PROTECTED]> writes:
> PostgreSQL OR is not commutative if left operand evaluates to NULL.
This is nonsense.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
Richard,
Seems to work here:
select (true or null) as a, (null or true) as b, (null or false) as c,
(false or null) as d;
a | b | c | d
---+---+---+---
t | t | |
(1 row)
I'm sorry for the wrong information.
Andrus.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To m
Andrus wrote:
>> I have a strange problem with the following condition in a SELECT:
>> AND (("TableData" = "inDate") OR ("inDate" IS NULL))
>>
>> it works perfectly when the input date in the function (inDate) matchs
>> a date in the table, but it does not work when the parameter inDate is
>> NULL.
I have a strange problem with the following condition in a SELECT:
AND (("TableData" = "inDate") OR ("inDate" IS NULL))
it works perfectly when the input date in the function (inDate) matchs
a date in the table, but it does not work when the parameter inDate is
NULL.
I recall the function with pg
Lucazeo <[EMAIL PROTECTED]> writes:
> It seems that ("inDate" IS NULL) never returns true, even when the
> parameter is null...
Exceedingly unlikely.
> What's wrong?
You have not provided enough context for anyone to guess.
regards, tom lane
--
Sent via pgsql-general m
I have a strange problem with the following condition in a SELECT:
AND (("TableData" = "inDate") OR ("inDate" IS NULL))
it works perfectly when the input date in the function (inDate) matchs
a date in the table, but it does not work when the parameter inDate is
NULL.
I recall the function with pga
