Re: SQL compatibility reminder: MySQL vs PostgreSQL

+1

Isn´t that a good time to think to put that question into the list of things PostgreSQL doesn´t want to do?

Cheers

________________________________
Von: Andrew Dunstan <andrew(at)dunslane(dot)net>
An: francois(dot)perou(at)free(dot)fr
CC: Josh Berkus <josh(at)agliodbs(dot)com>; Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>; pgsql-hackers(at)postgresql(dot)org; dpage(at)pgadmin(dot)org
Gesendet: Samstag, den 6. März 2010, 22:01:06 Uhr
Betreff: Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

François Pérou 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.
>

This is just fantasy. Doing this will destabilize Postgres, cost us hugely in maintenance effort and LOSE us users.

If we do this why the heck should we stop there? Why shouldn't we replicate the broken behaviour of every major database out there?

It's really time for you to stop making this suggestion, once and for all. It is just not going to happen. Moreover MySQL appears to be fracturing into a bunch of different forks, so why now, of all times, would we want to adopt its broken syntax?

cheers

andrew

-- Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com