Re: ECPG. Badly stuck

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: Jasbinder Bali <jsbali(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ECPG. Badly stuck
Date: 2006-07-26 10:29:09
Message-ID: 20060726102909.GA5151@mcknight.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jul 25, 2006 at 02:46:02PM -0400, Jasbinder Bali wrote:
> Tried writing the follwoing code but doesn't give me any result.
> Don't know if i have to do somethin else apart from what i've already done.

There are many ways your program can fail before actually reaching the
select line but you won't notice because your program fails to check for
errors. Do at least insert a

exec sql whenever sqlerror do sqlprint();

before connecting to the server. For more information on error handling,
see

http://www.postgresql.org/docs/8.1/interactive/ecpg-errors.html

While developing you can also switch on debug output with the ECPGdebug
function described here:

http://www.postgresql.org/docs/8.1/interactive/ecpg-library.html

Joachim

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Meskes 2006-07-26 11:08:34 Re: ECPG. Badly stuck
Previous Message Isak Hansen 2006-07-26 10:13:36 Constraint on an aggregate? (need help writing trigger, i think..)