[Keystone Slip # 4] ECPG declare cursor parses, but no data struct in Postgres. - Mailing list pgsql-bugs

From webmaster@postgresql.org
Subject [Keystone Slip # 4] ECPG declare cursor parses, but no data struct in Postgres.
Date
Msg-id 199907241659.MAA40525@hub.org
Whole thread Raw
List pgsql-bugs
---------------------------------------------------------------------------
Slip number -----: 4
Problem ---------: ECPG declare cursor parses, but no data struct in Postgres.
Opened by -------: adroffne@advance.net on 07/23/99 11:16
Assigned To -----: scrappy
---------------------------------------------------------------------------
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/24/99 12:59 by scrappy:
Current tech changed to scrappy from momjian
Status changed to A from U

---------------------------------------------------------------------------
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:

Previous
From: webmaster@postgreSQL.org
Date:
Subject: [Keystone Slip # 10] make of 6.5.1 failed with flex 2.5.4
Next
From: webmaster@postgresql.org
Date:
Subject: [Keystone Slip # 5] Query consumes all RAM on machine (OR + LIKE problem)