Re: MySQL search query is not executing in Postgres DB - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: MySQL search query is not executing in Postgres DB
Date
Msg-id 50C4C761.1080609@Yahoo.com
Whole thread Raw
In response to Re: MySQL search query is not executing in Postgres DB  (Peter Eisentraut <peter_e@gmx.net>)
List 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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: Simon Riggs
Date:
Subject: Re: Review of Row Level Security