| From: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Peter Eisentraut' <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: A problem presentaion about ECPG, DECLARE STATEMENT |
| Date: | 2019-09-18 11:46:17 |
| Message-ID: | TY2PR01MB24436EBE6378D2285DF4CEF8F58E0@TY2PR01MB2443.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Peter,
I want to complement about another purpose.
This is that declaring an SQL identifier.
In the oracle (and maybe DB2), the following example is not allowed:
...
EXEC SQL DECLARE cursor CURSOR FOR stmt;
^^^^
EXEC SQL PREPARE stmt FOR "SELECT ..."
...
This is caused because these preprocessor cannot recognize stmt as an SQL identifier and
throw an error.
I think DB2 might focus on here, so AT clause is not important for them.
But ECPG can accept these sentences, so it has no meaning for postgres.
That is why I did not mention about it and I focused on the omission of AT clause.
Hayato Kuroda
Fujitsu LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2019-09-18 12:09:12 | Re: [PATCH] Speedup truncates of relation forks |
| Previous Message | kuroda.hayato@fujitsu.com | 2019-09-18 11:41:33 | RE: A problem presentaion about ECPG, DECLARE STATEMENT |