| 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)jp(dot)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)jp(dot)fujitsu(dot)com> |
| Subject: | Re: SQL statement PREPARE does not work in ECPG |
| Date: | 2019-03-24 01:03:43 |
| Message-ID: | 677ecdf5b9b2b4ac71dc4f31da9139544d2398df.camel@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matsumura-san,
> Therefore, I think that the quoting statement name is needed in
> PREPARE/EXECUTE case, too.
I agree that we have to accept a quoted statement name and your
observations are correct of course, I am merely wondering if we need
the escaped quotes in the call to the ecpg functions or the libpq
functions.
> > I would prefer to merge as much as possible, as I am afraid that if
> > we
> > do not merge the approaches, we will run into issues later. There
> > was a
> > reason why we added PQprepare, but I do not remember it from the
> > top of
> > my head. Need to check when I'm online again.
>
> I will also consider it.
Thank you.
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 | Chapman Flack | 2019-03-24 01:21:57 | Re: The two "XML Fixes" patches still in need of review |
| Previous Message | David Rowley | 2019-03-24 00:17:18 | Re: [HACKERS] PATCH: multivariate histograms and MCV lists |