Re: MySQL search query is not executing in Postgres DB

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MySQL search query is not executing in Postgres DB
Date: 2012-12-09 17:16:17
Message-ID: 50C4C761.1080609@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I am aware that in the case at hand, the call to make_fn_arguments() is
with the only possible candidate function, so changing COERCE_IMPLICIT
to COERCE_ASSIGNMENT inside of make_fn_arguments() is correct. But I
wonder if this may have any unwanted side effects for other code paths
to make_fn_arguments(), like from optimizer/util/clauses.c or from
parser/parse_oper.c. I'm not saying it does, just asking if that could
be the case.

Jan

--
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-12-09 17:21:46 Re: Review of Row Level Security
Previous Message Simon Riggs 2012-12-09 17:15:16 Re: Support for REINDEX CONCURRENTLY