Re: Is this a bug in ECPG?

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: "Wang, Jing" <jingw(at)fast(dot)au(dot)fujitsu(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, "Arulappan, Arul Shaji" <arul(at)fast(dot)au(dot)fujitsu(dot)com>, "Boguk, Maksym" <maksymb(at)fast(dot)au(dot)fujitsu(dot)com>
Subject: Re: Is this a bug in ECPG?
Date: 2013-09-06 07:57:34
Message-ID: 52298AEE.808@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013-09-06 02:57 keltezéssel, Wang, Jing írta:
>
> Hi,
>
> ECPG don't support the following scenario:
>
> char cur_name = "cur1";
>
> EXEC SQL DECLARE :cur_name CURSOR FOR ...
>
> EXEC SQL OPEN :cur_name;
>
> EXEC SQL FETCH cur1 INTO...
>
> ...
>
> EXEC SQL CLOSE :cur_name;
>
> An compile error will occur for above codes because ECPG can't find the "cur1".
>

Of course it cannot find it, ECPG doesn't interpret the content of the variable,
so it cannot know it is "cur1".

> But it does support the following scenario:
>
> char cur_name = "cur1";
>
> EXEC SQL DECLARE :cur_name CURSOR FOR ...
>
> EXEC SQL OPEN :cur_name;
>
> EXEC SQL FETCH :cur_name INTO...
>
> ...
>
> EXEC SQL CLOSE cur1;
>
> Does the second scenario is a bug for ECPG?
>

Actually, it looks like it is a bug.

> Will anyone use the second scenario to close an CURSOR that is named by a variable?
>

Not very likely.

> Kind regards,
>
> Jing
>

--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
http://www.postgresql.at/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Szymon Guz 2013-09-06 08:13:43 Failed to autoconvert '1' to text.
Previous Message Szymon Guz 2013-09-06 07:30:36 Re: Levenshtein Distance with more than 255 characters