I haven't seen any feedback on this report, but FYI... I worked around
this problem by rewriting my code to use a dynamic prepared statement
EXEC SQL MOVE FORWARD :RowMove IN Sniffer;
const char mover = "MOVE FORWARD ? IN Sniffer";
EXEC SQL PREPARE MoverSQL FROM :mover;
EXEC SQL EXECUTE MoverSQL USING :RowMove;
EXEC SQL DEALLOCATE PREPARE MoverSQL;
Assuming the new restriction on the original "MOVE FORWARD" is
intentional, it would be nice to see a warning that code changes are
required get into the documentation.
[mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Scott Bailey
Sent: Monday, October 29, 2007 11:45 AM
Subject: [BUGS] BUG #3706: ecpg regression: "MOVE FORWARD"
The following bug has been logged online:
Bug reference: 3706
Logged by: Scott Bailey
Email address: scott(dot)bailey(at)eds(dot)com
PostgreSQL version: 8.3beta1
Operating system: Tru64
Description: ecpg regression: "MOVE FORWARD"
The following statement:
exec sql MOVE FORWARD :RowMove IN Sniffer;
which worked correctly in 8.2.4 and previous versions, now fails to
in 8.3beta1; I receive the following error message:
ERROR: fetch/move count must not be a variable.
This sucks and I couldn't find anything about it in the TODO list or
Notes. Is this unintentional, or should I be recoding my program to use
loop to move forward 1 row at a time?
In response to
pgsql-bugs by date
|Next:||From: Andreas Pflug||Date: 2007-11-02 20:00:59|
|Subject: BUG #3716: utf8 crash with replace|
|Previous:||From: Thomas H.||Date: 2007-11-02 19:52:43|
|Subject: Re: BUG #3715: StackBuilder failing|