From: | Russ Brown <pickscrape(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql vs mysql |
Date: | 2007-02-21 11:50:00 |
Message-ID: | 45DC31E8.2070807@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This can (I discovered yesterday) be fixed by adding ONLY_FULL_GROUP_BY
to the sql_mode setting.
As Ron mentioned though that can be happily overridden on a per-session
basis so it's not as 'strict' as it makes out...
Chad Wagner wrote:
> On 2/20/07, *gustavo halperin* <ggh(dot)develop(at)gmail(dot)com
> <mailto:ggh(dot)develop(at)gmail(dot)com>> wrote:
>
> I have a friend that ask me why postgresql is better than mysql.
> I personally prefer posgresql, but she need to give in her work 3 or 4
> strong reasons for that. I mean not to much technical reasons. Can you
> give help me please ?
>
>
> How about the fact that MySQL accepts the following query as legal:
>
> SELECT foo, bar, COUNT(*)
> FROM baz
> GROUP BY foo
>
> And produces, naturally, an unexpected result instead of an error.
> Totally annoying, I don't know if it was ever fixed. It seems that
> MySQL's parser is generally weak at syntax validation in it's default
> configuration.
>
>
> --
> Chad
> http://www.postgresqlforums.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2007-02-21 12:01:25 | Re: Slow running to_tsvector (tsearch2 in PG 8.2.3) |
Previous Message | MG | 2007-02-21 11:48:27 | Re: pg_dump: [tar archiver] write error appending to tar archive |