| 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-20 23:17:02 |
| Message-ID: | 45B2A2EE.6060505@cox.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's exactly what I would do...
On 01/20/07 17:09, Michael Nolan wrote:
> This is a generated query in a web form where there could be a series of 12
> digit event IDs input by the user, hence using the 'in' form. This is
> slightly lazy programming on my part, but it makes little difference in
> either PostgreSQL or MySQL whether I use = or 'in'.
> --
> Mike Nolan
>
> On 1/20/07, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> wrote:
>>
>>
>>
>> Is this query created by an application? I.e, there might be a list
>> of PLR_EVENTIDs?
>>
>> If so, I understand why it is like it is. Otherwise, why not make
>> it a direct equality?
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFsqLuS9HxQb37XmcRAuaeAKCBXTAg7gfhWk/p4sv4OG2Rdtsc5gCeI71c
Nw4vY1tttyY3+5JRY4t89UE=
=jkEY
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-21 01:14:53 | Re: More grist for the PostgreSQL vs MySQL mill |
| Previous Message | Michael Nolan | 2007-01-20 23:09:08 | Re: More grist for the PostgreSQL vs MySQL mill |