From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: Potential bug in postgres 8.2.4
Date: Thu, 24 May 2007 13:51:15 +0200
User-Agent: KMail/1.9.5
Cc: Tomas Doran <bobtfish@bobtfish.net>, tdoran@venda.com
References: <3D2864D1-BF64-4609-B307-1C70A4FE503F@bobtfish.net>
In-Reply-To: <3D2864D1-BF64-4609-B307-1C70A4FE503F@bobtfish.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200705241351.15767.peter_e@gmx.net>

Am Donnerstag, 24. Mai 2007 13:20 schrieb Tomas Doran:
> CREATE TABLE testtable (
>      col1   char(1),
>     data   text
> );

> The following queries all work:
> INSERT INTO testtable (col1, data) VALUES (3::int, 'foobarbazquux');
> SELECT * FROM testtable WHERE col1 = 3::int;
> SELECT * FROM testtable WHERE col1 IN (1);
> SELECT * FROM testtable WHERE col1 IN (1::int);

> However these querys fail on 8.2.4, but work correctly on 8.1:
> SELECT * FROM testtable WHERE col1 IN (1::int, 2::int);
> SELECT * FROM testtable WHERE col1 IN (1, 2);

All of this is strictly speaking incorrect anyway.  And the queries that do 
work will most likely start not working in a future version.  All of this is 
a gradual effort to reduce excessive automatic type casting.

I suggest you fix your application.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/