Just so that we can snip this thread, we've confirmed that free cursor
and free statement do not affect sqlca structure elements sqlcode and
sqlstate.
Michael Fuhr wrote:
On Mon, Aug 29, 2005 at 04:39:36PM -0500, andy rost wrote:
I worked on my problem a little further and have a little more
On Mon, Aug 29, 2005 at 04:39:36PM -0500, andy rost wrote:
> I worked on my problem a little further and have a little more
> information to share. The declare statement that fails consistently
> follows a select statement that returns zero rows (and sqlcode 100 and
> sqlstate '02000'). If I omm
I worked on my problem a little further and have a little more
information to share. The declare statement that fails consistently
follows a select statement that returns zero rows (and sqlcode 100 and
sqlstate '02000'). If I ommit the select statement from the code or set
sqlcode to 0 before c
Sure. I'm using ECPG (ecpg -t -r no_indicator -C INFORMIX) in a TRU64
operating system for PostgreSQL version 8.0.2. By occasionally, I mean
that I don't observe this problems for each declare and free statement
that I've encoded - only for a subset of those commands. But I do
observe this prob
On Mon, Aug 29, 2005 at 02:28:24PM -0500, andy rost wrote:
> I'm in the process of porting Informix ESQL to PostgreSQL. I
> occasionally get sqlcode = 100 and sqlstate = 02000 when declaring
> cursors or freeing prepared statements. Is this normal? For example:
>
> $declare loop1 cursor with
