Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 30E4564FCD6 for ; Mon, 29 Dec 2008 07:21:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 29272-03 for ; Mon, 29 Dec 2008 07:21:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail16.svc.cra.dublin.eircom.net (mail16.svc.cra.dublin.eircom.net [159.134.118.215]) by mail.postgresql.org (Postfix) with SMTP id DBCA164FCC7 for ; Mon, 29 Dec 2008 07:21:28 -0400 (AST) Received: (qmail 7306 messnum 3317910 invoked from network[86.40.228.28/86-40-228-28-dynamic.b-ras3.mvw.galway.eircom.net]); 29 Dec 2008 11:21:26 -0000 Received: from 86-40-228-28-dynamic.b-ras3.mvw.galway.eircom.net (HELO ?127.0.0.1?) (86.40.228.28) by mail16.svc.cra.dublin.eircom.net (qp 7306) with SMTP; 29 Dec 2008 11:21:26 -0000 Message-ID: <4958B2B4.9060501@iol.ie> Date: Mon, 29 Dec 2008 11:21:24 +0000 From: Raymond O'Donnell Reply-To: rod@iol.ie User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: kulmacet101@kulmacet.com CC: Andrew McMillan , pgsql-php@postgresql.org Subject: Re: You might need to add explicit type casts. References: <49584E7C.6090409@kulmacet.com> <13f61b6746f3518943cc921d039e9b70.squirrel@webmail.kulmacet.com> In-Reply-To: <13f61b6746f3518943cc921d039e9b70.squirrel@webmail.kulmacet.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 081228-0, 28/12/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/10 X-Sequence-Number: 3944 On 29/12/2008 04:17, kulmacet101@kulmacet.com wrote: > I also found that the WHERE statements were not properly quoted, a 101 > mistake. > > WHERE id = 469 => WHERE id = '469' Yes, this commonly bites people moving from earlier versions of PostgreSQL to 8.3 - a lot of automatic casts have been removed. The original error message suggests that this was your problem all along. I'm curious as to why you've defined the "id" column as VARCHAR when you seem to expect it to hold integers....unless of course there will be non-numeric characters there also? Ray. ------------------------------------------------------------------ Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland rod@iol.ie Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals ------------------------------------------------------------------