Skip site navigation (1) Skip section navigation (2)

Re: MySQL search query is not executing in Postgres DB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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-08-27 23:13:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I agree that redefining the lexer behavior is a can of worms.  What I
> don't understand is why f(2+2) can't call f(smallint) when that's the
> only extant f.  It seems to me that we could do that without breaking
> anything that works today: if you look for candidates and don't find
> any, try again, allowing assignment casts the second time.

Yeah, possibly.  Where would you fit that in the existing sequence of

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2012-08-27 23:35:14
Subject: Re: FATAL: bogus data in lock file "": ""
Previous:From: Bruce MomjianDate: 2012-08-27 22:43:56
Subject: Re: Incorrect behaviour when using a GiST index on points

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group