Skip site navigation (1) Skip section navigation (2)

Re: Interesting ECPG error

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: "Owens, Steve" <Steve(dot)Owens(at)xerox(dot)com>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: Interesting ECPG error
Date: 2004-06-28 11:03:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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 look down in ECPGexecute and found 3 places where the TOO_FEW_ARGUMENTS error is being returned. If I get a chance, I'll see if 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 Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

pgsql-interfaces by date

Next:From: Carlos Ojea CastroDate: 2004-06-29 11:03:28
Subject: : query using kylix (delphi)
Previous:From: Michael MeskesDate: 2004-06-27 12:33:03
Subject: Re: ECPG scoping

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group