| From: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | A problem presentaion about ECPG, DECLARE STATEMENT |
| Date: | 2019-09-11 09:46:38 |
| Message-ID: | TY2PR01MB2443EC8286995378AEB7D9F8F5B10@TY2PR01MB2443.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear ALL,
I want to report and consult about DECLARE STATEMENT.
This feature, committed last February, has some bugs.
* This is not thread-independent.
* If some cursors are declared for the same SQL identifier,
only one cursor you declared at last is enabled.
* This syntax does not have oracle compatibility.
In order to modify bugs, I think many designs, implementations,
and specifications should be changed.
Any operations will be done at the preprocessor process, like #define
macro in C.
It will take about 2 or 3 weeks to make a patch.
Is it acceptable for PG12?
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
E-Mail:kuroda(dot)hayato(at)fujitsu(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-09-11 09:50:59 | Re: doc: update PL/pgSQL sample loop function |
| Previous Message | Pavel Stehule | 2019-09-11 08:54:42 | Re: don't see materialized views in information_schema |