From: | David Christensen <david(at)endpoint(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Wolfgang Wilhelm" <wolfgang20121964(at)yahoo(dot)de>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
Date: | 2010-03-08 15:24:41 |
Message-ID: | 1D1F220C-F844-4C84-91CD-7BE0C8220F32@endpoint.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Mar 8, 2010, at 9:16 AM, Kevin Grittner wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Wolfgang Wilhelm <wolfgang20121964(at)yahoo(dot)de> wrote:
>
>>> Isn*t that a good time to think to put that question into the
>>> list of things PostgreSQL doesn*t want to do?
>>
>> Yes.
>
> Done.
>
> http://wiki.postgresql.org/wiki/Todo#Features_We_Do_Not_Want
Does this conflict conceptually with the item from "Exotic Features"
on the same page?:
* Add pre-parsing phase that converts non-ISO syntax to supported syntax
This could allow SQL written for other databases to run without
modification.
Regards,
David
--
David Christensen
End Point Corporation
david(at)endpoint(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-08 15:59:19 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
Previous Message | Kevin Grittner | 2010-03-08 15:16:11 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-08 15:59:19 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
Previous Message | Kevin Grittner | 2010-03-08 15:16:11 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |