Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6QIWkf60488 for ; Thu, 26 Jul 2001 14:32:46 -0400 (EDT) (envelope-from aalang@rutgersinsurance.com) Received: from nj012 ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id OAA28901 for ; Thu, 26 Jul 2001 14:54:15 -0400 Message-ID: <015f01c11601$b3fc0160$330a0a0a@rutgersinsurance.com> From: "Adam Lang" To: References: <20010726180500.15047.qmail@web13002.mail.yahoo.com> Subject: Re: Re: how to determine where a select statement fails Date: Thu, 26 Jul 2001 14:35:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200107/30 X-Sequence-Number: 487 Basically, the person wants to know which where clause caused the query to return 0 results. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Brent R. Matzelle" To: "Heather Johnson" ; Sent: Thursday, July 26, 2001 2:05 PM Subject: [PHP] Re: how to determine where a select statement fails > I'm not sure if I understand what your problem is. If a query > does not return any rows (pg_numrows() < 1) then that is not > really a "failure". If the SQL was incorrect then I would > suggest printing it to the browser (echo $query) and pasting it > in a query program like psql or winsql to determine which line > of code was incorrect. > > Brent