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

From Merlin Moncure
Subject Re: SQL compatibility reminder: MySQL vs PostgreSQL
Date
Msg-id b42b73151003050728s1ea2edf7w93fba3d6b1540d50@mail.gmail.com
Whole thread Raw
In response to SQL compatibility reminder: MySQL vs PostgreSQL  (François Pérou <francois.perou@free.fr>)
List pgsql-hackers
2010/3/5 François Pérou <francois.perou@free.fr>:
> => All non-aggregate fields must be present in the GROUP BY clause
> http://drupal.org/node/555530

My take is that this is never going to happen unless we are strictly
talking about cases where the non-aggregate fields can be
unambiguously determined.  If we aren't, mysql is wrong to allow this,
and developers that depend on it are wrong, and that is pretty much
all you are ever going to get from this list. :-)

The other stuff is mainly tangential fluff issues (takes 1% extra
effort to write portable sql for) except for the flexible multi table
delete, which would be nice although I wouldn't expect a strict copy
of mysql syntax.  I am personally looking at writeable CTE (which
didn't make 9.0) to do most of the things I would need to do with a
multi table delete feature, plus a quite a few other things.

merlin


pgsql-hackers by date:

Previous
From: Tim Bunce
Date:
Subject: Core dump running PL/Perl installcheck with bleadperl [PATCH]
Next
From: Robert Haas
Date:
Subject: Re: SQL compatibility reminder: MySQL vs PostgreSQL