Re: php and postgres - too many queries too fast?

From: Richard Huxton <dev(at)archonet(dot)com>
To: Tom Hart <tomhart(at)coopfed(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: php and postgres - too many queries too fast?
Date: 2007-11-06 08:23:12
Message-ID: 47302470.2050802@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Hart wrote:
>
> It turns out that for some reason it didn't like to UPDATE when I was
> using a text type field (specifically an empty text field) in the WHERE
> clause. To remedy this, I instructed PHP to not use a field in the WHERE
> clause if the destination type was 'text', and now we're working
> beautifully (2.405 seconds to run the script through 1566 rows, running
> updates on 1563 of them). Now I just need to figure out what's going on
> with those 3 rogue rows.

Its almost certainly not an empty text field, but a NULL one, see Jeff's
reply to your original message.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Reg Me Please 2007-11-06 08:54:58 How to create primary key
Previous Message rihad 2007-11-06 07:38:29 any way for ORDER BY x to imply NULLS FIRST in 8.3?