Re: php and postgres - too many queries too fast? - Mailing list pgsql-general

From Richard Huxton
Subject Re: php and postgres - too many queries too fast?
Date
Msg-id 47302470.2050802@archonet.com
Whole thread Raw
In response to Re: php and postgres - too many queries too fast?  (Tom Hart <tomhart@coopfed.org>)
List 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

pgsql-general by date:

Previous
From: rihad
Date:
Subject: any way for ORDER BY x to imply NULLS FIRST in 8.3?
Next
From: Reg Me Please
Date:
Subject: How to create primary key