Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 8402E4769FE for ; Fri, 6 Dec 2002 14:08:06 -0500 (EST) Received: from mail1.ihs.com (mail1.ihs.com [170.207.70.222]) by postgresql.org (Postfix) with ESMTP id 6A70A476B34 for ; Fri, 6 Dec 2002 14:06:31 -0500 (EST) Received: from css120.ihs.com (css120.ihs.com [170.207.105.120]) by mail1.ihs.com (8.12.6/8.12.6) with ESMTP id gB6J4hXY009245; Fri, 6 Dec 2002 12:04:44 -0700 (MST) Date: Fri, 6 Dec 2002 12:01:11 -0700 (MST) From: "scott.marlowe" To: Cc: Mark Nelson , Subject: Re: getting integer result from 4.1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailBodyFilter: Message body has not been filtered X-MailScanner: Found to be clean X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/10 X-Sequence-Number: 1685 On Fri, 6 Dec 2002 brew@theMode.com wrote: > > > I have an update statement that queries a db and updates wheere > > it finds matches. > > Ooops, I just noticed it was an update statement, but there is a function > for that, too, pg_affected_rows, I think. Note that the pg_affected_rows was added as of php version 4.2.0, so you'll need to upgrade from 4.1 to get that functionality. 4.3 is in RC2 or so right now, so you might wanna wait a week or two for the new version of php to come out.