Re: BUG #2242: Inconsistent casting in query with literal vs query with parameter - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2242: Inconsistent casting in query with literal vs query with parameter
Date
Msg-id 6732.1139323769@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2242: Inconsistent casting in query with literal vs query with parameter  ("Matthew Bellew" <postgres@bellew.net>)
List pgsql-bugs
"Matthew Bellew" <postgres@bellew.net> writes:
> In the script below, I'd expect all four queries to return 10 rows
> (1,2,3,4,5,10,20,30,40,50).  However, function bystr() returns two rows
> (1,10).  Clearly, in this one case the query processor is casting the column
> to the parameter type, rather than the other way around.  The optimizer
> should always preferentially cast the parameter to the type of the column.

I see no bug here.  You are confused about the difference between an
unknown literal ('100') and a value that is actually declared to be of
type text.  See
http://www.postgresql.org/docs/8.1/static/typeconv.html

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2245: pg_dump doesn't dump expressions with sequence in DEFAULT setting for some column in table
Next
From: "Matej Rizman"
Date:
Subject: BUG #2243: Postgresql fails to finish some queries