Re: MySQL search query is not executing in Postgres DB

Jeff Davis <pgsql@j-davis.com>

From: Jeff Davis <pgsql@j-davis.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Greg Stark <stark@mit.edu>, Bruce Momjian <bruce@momjian.us>, Andrew Dunstan <andrew@dunslane.net>, premanand <kottiprem@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-11-27T19:59:18Z
Lists: pgsql-hackers
On Tue, 2012-11-27 at 14:13 -0500, Robert Haas wrote:
> I do think that applying some kind of explicit flag to the function
> indicating whether it should allow implicit assignment
> casting/implicit casting to text/overloading/whatever is a possibly
> interesting alternative.  It seems clear from our system catalogs that
> implicit casting to text is sometimes a desirable behavior and
> sometimes not, so it's reasonable to think that perhaps we should put
> that under user control.  What I like about "my" proposal (really
> Tom's idea) is that it seems like it solves a pretty high percentage
> of the problem cases without requiring any explicit user action.

What user action are you concerned about? If we (eventually) made the
non-overloaded case the default, would that resolve your concerns?

Regards,
	Jeff Davis