| From: | "Wang, Jing" <jingw(at)fast(dot)au(dot)fujitsu(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Cc: | "Arulappan, Arul Shaji" <arul(at)fast(dot)au(dot)fujitsu(dot)com>, "Boguk, Maksym" <maksymb(at)fast(dot)au(dot)fujitsu(dot)com> |
| Subject: | Is this a bug in ECPG? |
| Date: | 2013-09-06 00:57:38 |
| Message-ID: | F9AB2AFB133B614987F30E6015FCBFC1ED6737@ack0102.au.fjanz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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".
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? Will anyone use the second
scenario to close an CURSOR that is named by a variable?
Kind regards,
Jing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Suzuki Hironobu | 2013-09-06 02:17:16 | Re: Question About WAL filename and its time stamp |
| Previous Message | Janek Sendrowski | 2013-09-05 23:00:10 | Levenshtein Distance with more than 255 characters |