Re: SQL compatibility reminder: MySQL vs PostgreSQL - Mailing list pgsql-hackers

From Robert Haas
Subject Re: SQL compatibility reminder: MySQL vs PostgreSQL
Date
Msg-id 603c8f071003080918n26f521flded1fa4607bf3405@mail.gmail.com
Whole thread Raw
In response to Re: SQL compatibility reminder: MySQL vs PostgreSQL  (David Fetter <david@fetter.org>)
Responses Re: SQL compatibility reminder: MySQL vs PostgreSQL
Re: SQL compatibility reminder: MySQL vs PostgreSQL
List pgsql-hackers
On Mon, Mar 8, 2010 at 12:10 PM, David Fetter <david@fetter.org> wrote:
> On Mon, Mar 08, 2010 at 11:58:20AM -0500, Jaime Casanova wrote:
>> On Mon, Mar 8, 2010 at 4:17 AM, Pierre C <lists@peufeu.com> wrote:
>> >
>> >> My opinion is that PostgreSQL should accept any MySQL syntax and
>> >> return warnings. I believe that we should access even innodb
>> >> syntax and turn it immediately into PostgreSQL tables. This would
>> >> allow people with no interest in SQL to migrate from MySQL to
>> >> PostgreSQL without any harm.
>> >
>> > A solution would be a SQL proxy (a la pgpool) with query
>> > rewriting.
>>
>> This sounds like a better idea...
>
> Aside from that little "halting problem" issue, it sounds wonderful.
> You do know that SQL is Turing-complete, right?

That seems largely irrelevant to the problem at hand.  It's not
impossible to do syntactic transformations from one Turing-complete
langauge to another; if it were, there could be no such thing as a
compiler.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Safe security
Next
From: Tim Bunce
Date:
Subject: Re: Safe security