BUG #17101: Inconsistent behaviour when querying with anonymous composite types
От
David G. Johnston
Тема
BUG #17101: Inconsistent behaviour when querying with anonymous composite types
Дата
Msg-id
CAKFQuwY0QBhO_NrXs-Zf_Hy2Xy5mu8eMrYXN9_araRjjNSpK_w@mail.gmail.com
Ответ на
Список
Дерево обсуждения
BUG #17101: Inconsistent behaviour when querying with anonymous composite types PG Bug reporting form <noreply@postgresql.org>
Re: BUG #17101: Inconsistent behaviour when querying with anonymous composite types Andrew Kiellor <akiellor@gmail.com>
Re: BUG #17101: Inconsistent behaviour when querying with anonymous composite types Tom Lane <tgl@sss.pgh.pa.us>
BUG #17101: Inconsistent behaviour when querying with anonymous composite types "David G. Johnston" <david.g.johnston@gmail.com>
Re: BUG #17101: Inconsistent behaviour when querying with anonymous composite types Tom Lane <tgl@sss.pgh.pa.us>
On Monday, July 12, 2021, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Andrew Kiellor <akiellor@gmail.com> writes:
> Sorry I omitted the output. It is as follows:
> psql:test.sql:14: ERROR: input of anonymous composite types is not implemented
> LINE 1: SELECT * FROM table1 WHERE column1 = '(0)';
> ^
I think this is operating as designed. I agree it'd be slightly more
convenient if the parser would infer that the RHS must be of the same
type as the LHS, but shoehorning that into the existing system design
seems problematic.
Why is the multi-valued IN expression special here? I would not expect the more-than-one element IN clause to obey different rules than a one element IN clause
-- passing scenario - IN query with multiple anonymous composite types
SELECT * FROM table1 WHERE column1 IN ('(0)', '(0)');
SELECT * FROM table1 WHERE column1 IN ('(0)', '(0)');
David J.
В списке pgsql-bugs по дате отправления
От: Tom Lane
Дата:
От: Tom Lane
Дата:
