Re: MySQL search query is not executing in Postgres DB

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <stark@mit.edu>, Bruce Momjian <bruce@momjian.us>, Andrew Dunstan <andrew@dunslane.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, premanand <kottiprem@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-08-28T17:32:51Z
Lists: pgsql-hackers
On Tue, Aug 28, 2012 at 1:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Also, right at the moment it's not clear to me whether there are any
> other cases besides integer literal vs smallint argument.  I think
> that's the only particularly surprising case within the numeric
> hierarchy --- and for non-numeric types, the literal is generally going
> to start out "unknown" so the whole problem doesn't arise.  I feel
> uncomfortable trying to invent general-purpose solutions to problems
> we have only one instance of ...

The other case that comes up regularly is someone trying to pass some
kind of number to a function such as LPAD().  There is only one LPAD()
so no ambiguity exists, but PostgreSQL doesn't even see that there's a
candidate.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company