| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Stark <stark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-12-14 07:30:42 |
| Message-ID: | 1355470242.11945.1.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2012-11-06 at 10:57 -0500, Robert Haas wrote:
> I did some experimentation with this. It seems that what Tom proposed
> here is a lot cleaner than what I proposed previously, while still
> increasing usability in many real-world cases. For example, in
> unpatched master:
It looks like we still haven't reached consensus on the design here. Are
we still discussing, or should this be moved to the next CF?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2012-12-14 07:35:29 | Re: MySQL search query is not executing in Postgres DB |
| Previous Message | Josh Kupershmidt | 2012-12-14 05:02:56 | Re: Multiple --table options for other commands |