| From: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | Pierre C <lists(at)peufeu(dot)com>, francois(dot)perou(at)free(dot)fr, Josh Berkus <josh(at)agliodbs(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, dpage(at)pgadmin(dot)org |
| Subject: | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Date: | 2010-03-08 17:14:46 |
| Message-ID: | e08cc0401003080914i61c492c7jb2cccd7865331217@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
2010/3/9 Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>:
> On Mon, Mar 8, 2010 at 4:17 AM, Pierre C <lists(at)peufeu(dot)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...
Could parser & rewriter hook be another solution here?
I'm completely against the wrong GROUP BY syntax from MySQL, but it is
also true that SQL is only an interface.
--
Hitoshi Harada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-03-08 17:18:31 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | David Fetter | 2010-03-08 17:10:02 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-03-08 17:18:31 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Tom Lane | 2010-03-08 17:14:14 | Re: Safe security |