X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4FA7AD1CA67 for ; Thu, 4 Mar 2004 15:18:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 00225-10 for ; Thu, 4 Mar 2004 11:18:50 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A9B46D1CA5F for ; Thu, 4 Mar 2004 11:18:47 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i24FIoRD025838; Thu, 4 Mar 2004 10:18:50 -0500 (EST) To: Gergely Czuczy Cc: pgsql-interfaces Subject: Re: libpq PQexecPrepared returns NULL In-reply-to: References: Comments: In-reply-to Gergely Czuczy message dated "Thu, 04 Mar 2004 16:03:52 +0100" Date: Thu, 04 Mar 2004 10:18:50 -0500 Message-ID: <25837.1078413530@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/7 X-Sequence-Number: 4786 Gergely Czuczy writes: > the strange thing is -- what i've forgot to mention -- is that > PQerrorMessage returns an empty string, so from this i don't know the > source of the error. That's messy. I'd recommend getting out a debugger and tracing through it to see exactly where it's failing. Or put in some printf's. There aren't that many paths that could return NULL. I guess one of them must be forgetting to set PQerrorMessage, which seems like a bug to me. Let us know what you find out. regards, tom lane