The expected behavior can be obtained by filtering out the null in
the subquery or by using "not exists" instead of "not in".
Here is an example:
CREATE TEMPORARY TABLE subquerytable (column1 INTEGER);
INSERT INTO subquerytable VALUES(2);
INSERT INTO subquerytable VALUES(NULL);
INSERT INTO subqu
On Tue, 2006-01-17 at 22:00 +, Daniel Afonso Heisler wrote:
> But, when i run the next query, it don't return TRUE
> # SELECT true WHERE 1 NOT IN (2,NULL,3);
These are not bugs.
The first statement is equivalent to
# select true where (1 != 2) and (1 != NULL) and (1 != 3);
1 != NULL is it
On Tue, Jan 17, 2006 at 10:00:28PM +, Daniel Afonso Heisler wrote:
> When i run the following query, postgreSQL return TRUE.
> # SELECT true WHERE 1 NOT IN (2,3);
>
> But, when i run the next query, it don't return TRUE
> # SELECT true WHERE 1 NOT IN (2,NULL,3);
The expression "1 NOT IN (2,
On Tue, 17 Jan 2006, Daniel Afonso Heisler wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2178
> Logged by: Daniel Afonso Heisler
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.X
> Operating system: Linux
> Description:NOT IN comm
The following bug has been logged online:
Bug reference: 2178
Logged by: Daniel Afonso Heisler
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.X
Operating system: Linux
Description:NOT IN command don't work
Details:
When i run the following query, postgreSQ
