From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | "Matsumura, Ryo" <matsumura(dot)ryo(at)jp(dot)fujitsu(dot)com>, "Takahashi, Ryohei" <r(dot)takahashi_2(at)fujitsu(dot)com>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com>, "Kuroda, Hayato" <kuroda(dot)hayato(at)fujitsu(dot)com> |
Subject: | Re: SQL statement PREPARE does not work in ECPG |
Date: | 2019-05-06 13:37:34 |
Message-ID: | 68e1dd6c44149c05a71b26dbe2f3d0d2d4582028.camel@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Matsumura-san,
> I defined the following specifications. Please review it.
>
> * ECPG can accept any valid PREPARE AS statement.
> * A char-type host variable can be used as the statement name of
> PREPARE AS,
> but its value is constrained by the specification of PREPARE AS.
> (e.g. the name cannot include double quotation.)
> * The above also allows the following. It's a bit strange but there
> is no reason
> for forbidding.
> prepare :st(type_list) as select $1
> * ECPG can accept EXECUTE statement with expression list that is
> allocated
> by both PREPARE FROM and PREPARE AS under the following
> constraints:
> - It must not include a using-clause.
> - The statement name must follow to the specification of PREPARE
> AS.
This look very reasonable to me. I'm completely fine with this
restriction being placed on PREPARE FROM.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-05-06 13:45:39 | Re: reindexdb & clusterdb broken against pre-7.3 servers |
Previous Message | Michael Paquier | 2019-05-06 12:49:47 | Re: reindexdb & clusterdb broken against pre-7.3 servers |