From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: More grist for the PostgreSQL vs MySQL mill |
Date: | 2007-01-22 14:34:32 |
Message-ID: | 45B4CB78.3050901@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/22/07 05:49, Peter Rosenthal wrote:
> Right,
>
> You also have to realize that your first query might return zero results,
> and MySQL (and maybe this is correct SQL behavior) balks at an empty value
> set "where table_id in ()".
>
> I would expect that giving the DBMS the whole picture of what you want to
> do, should allow it to make better decisions on how to retrieve the data.
>
> MySQL Inefficiencies like this seem to hit the performance of a highly
> normalized database design hard.
<SNARKY_REMARK>
Do MySQL "designers" even know what data normalization is?
</SNARKY_REMARK>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFtMt4S9HxQb37XmcRAn3LAKDQo5NK1Htd/QrQ6h15iBS8xZU2NgCfW/Ak
HBliUtTkRP0yH8MtuabNCjE=
=b8aT
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Moritz Bayer | 2007-01-22 14:43:42 | Loop in loop |
Previous Message | Ron Johnson | 2007-01-22 14:30:53 | Re: security question |