Re: MySQL search query is not executing in Postgres DB

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, Pavel Stehule <pavel.stehule@gmail.com>, Bruce Momjian <bruce@momjian.us>, Jeff Davis <pgsql@j-davis.com>, Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Greg Stark <stark@mit.edu>, Andrew Dunstan <andrew@dunslane.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, premanand <kottiprem@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-11-27T22:41:19Z
Lists: pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> writes:
> ... I think if you relaxed
> the function sigs of a few functions on this page
> (http://www.postgresql.org/docs/9.2/interactive/functions-string.html),
> most reported problems would go away.

That's an interesting way of approaching it.  Do we have any data on
exactly which functions people do complain about?

> One thing that worries me is introducing ambiguous cases where
> previously there weren't any though.

Right, but at least we'd be confining the ambiguity to a small number
of function names.  Tweaking the casting rules could have a lot of
unforeseen consequences.

			regards, tom lane