Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... ) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... )
Date
Msg-id 29692.1192849524@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... )  ("Dawid Kuroczko" <qnex42@gmail.com>)
Responses Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... )
List pgsql-bugs
"Dawid Kuroczko" <qnex42@gmail.com> writes:
> What troubles me here is that surprise factor is unusally high here.
> While I understand mechanics why IN (1) works while IN (1,2) does not,
> I think random developers are going to be confused.

If you're not testing against 8.3 then this argument doesn't carry much
weight.  8.3 will reject *both* cases in the examples you've mentioned.

> PS: I wonder why explicitly using IN (ARRAY[...]) works.

Um, it does not work AFAICS:

regression=# select 'foo'::varchar in (array[1,2,3]);
ERROR:  operator does not exist: character varying = integer[]
LINE 1: select 'foo'::varchar in (array[1,2,3]);
                              ^
HINT:  No operator matches the given name and argument type(s). You may need to add explicit type casts.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Dawid Kuroczko"
Date:
Subject: Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... )
Next
From: "Gary Chambers"
Date:
Subject: BUG #3682: Incomplete database restore