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

[Keystone Slip # 4] ECPG declare cursor parses, but no data struct in Postgres.

From: webmaster(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: [Keystone Slip # 4] ECPG declare cursor parses, but no data struct in Postgres.
Date: 1999-07-23 16:52:24
Message-ID: 199907231652.MAA15926@hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
---------------------------------------------------------------------------
Slip number -----: 4
Problem ---------: ECPG declare cursor parses, but no data struct in Postgres.
Opened by -------: adroffne(at)advance(dot)net on 07/23/99 11:16
Assigned To -----: momjian
---------------------------------------------------------------------------
Summary:
The embedded SQL statement:
EXEC SQL DECLARE cursor_name CURSOR FOR select_statement;
does form a ECPGdo() call with the preprocessor. Yet, when the code runs, it generates the error:
portal "cursor_name" not defined
Does Postgres (6.5) know how to handle cursor declarations?
---------------------------------------------------------------------------
History:
07/23/99 12:52 by scrappy:
Dependency changed to 0 from 
Current tech changed to momjian from 
Contact changed to  from ANONYMOUS
Scheduled Close Date changed to 0 from 
Scheduled Open Date changed to 0 from 
Public setting changed to 1 from 0
Policy changed to 0

---------------------------------------------------------------------------


          Full information on this slip is available at:
http://www.postgresql.org/bugs/visitor.php3?sid=4&v_func=zoom

---------------------------------------------------------------------------
This message was generated automatically by Keystone at http://www.postgresql.org


pgsql-bugs by date

Next:From: webmasterDate: 1999-07-23 19:27:44
Subject: [Keystone Slip # 7] Backend crashes with 'vacuum analyze', new in 6.5.1
Previous:From: webmasterDate: 1999-07-23 16:50:40
Subject: [Keystone Slip # 5] Query consumes all RAM on machine (OR + LIKE problem)

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