Re: Interesting ECPG error - Mailing list pgsql-interfaces

From Michael Meskes
Subject Re: Interesting ECPG error
Date
Msg-id 20040628110338.GA31520@trantor.fam-meskes.de
Whole thread Raw
In response to Interesting ECPG error  ("Owens, Steve" <Steve.Owens@xerox.com>)
List pgsql-interfaces
On Tue, Jun 22, 2004 at 01:41:58PM -0400, Owens, Steve wrote:
> Ok, I've attached the log file and a tgz file containing a simple test case that duplicates the problem. I took a
lookdown in ECPGexecute and found 3 places where the TOO_FEW_ARGUMENTS error is being returned. If I get a chance, I'll
seeif I can generate an unstripped version of the ECPG library and get more information.
 

I think I found it. The reason is that your function does return a
tuple, but your statement offers no variable where this tuple can be
stored. I haven't looked at your function so far, but the log file shows
that PQresultStatus is PGRES_TUPLES_OK. So ecpg tries to read that
variable, which is NULL btw, into a variable but does not find one. Thus
the error message.

Michael

-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


pgsql-interfaces by date:

Previous
From: Michael Meskes
Date:
Subject: Re: ECPG scoping
Next
From: Carlos Ojea Castro
Date:
Subject: : query using kylix (delphi)