| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, premanand <kottiprem(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MySQL search query is not executing in Postgres DB |
| Date: | 2012-11-27 22:41:19 |
| Message-ID: | 5928.1354056079@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-11-27 23:25:39 | Re: MySQL search query is not executing in Postgres DB |
| Previous Message | Jeff Davis | 2012-11-27 22:24:16 | Re: MySQL search query is not executing in Postgres DB |