From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | glennwidener(at)gmail(dot)com |
Subject: | BUG #16945: where value in (null) set results inconsistent |
Date: | 2021-03-28 21:44:47 |
Message-ID: | 16945-b758f752890b2b8e@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16945
Logged by: Glenn Widener
Email address: glennwidener(at)gmail(dot)com
PostgreSQL version: 11.5
Operating system: Windows 10
Description:
Pursuant to a fix in Hibernate, that uses "where value in (null)" as a
workaround for several DB's not handling "where value in ()":
https://hibernate.atlassian.net/browse/HHH-8091
Consider this inconsistency:
test-db=> select id from project_type_variants where id in (0);
id
----
(0 rows)
test-db=> select id from project_type_variants where id in (null);
id
----
(0 rows)
test-db=> select id from project_type_variants where id not in (0);
id
----
1
2
3
(3 rows)
test-db=> select id from project_type_variants where id not in (null);
id
----
(0 rows)
Needs to work consistently, because (null) is a required workaround for:
test-db=> select id from project_type_variants where id in ();
ERROR: syntax error at or near ")"
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2021-03-29 02:34:57 | Re: BUG #16922: In cascading replication, a standby server aborted when an upstream standby server promoted |
Previous Message | PG Bug reporting form | 2021-03-26 10:50:41 | BUG #16944: when creating postGIS 2.5.4 extension for PostgreSQL10 is missing |