Re: A problem presentaion about ECPG, DECLARE STATEMENT
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Meskes <meskes@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>, pgsql-hackers@lists.postgresql.org
Date: 2019-09-27T18:14:40Z
Lists: pgsql-hackers
On Mon, Sep 16, 2019 at 01:12:17PM +0200, Peter Eisentraut wrote: > Moreover, I've been wondering about the behavior detail given in the > table at > <https://www.postgresql.org/docs/devel/ecpg-sql-declare-statement.html>. > In scenario 3, the declare statement says con1 but the subsequent > dynamic statement says con2, and as a result of that, con1 is used. > This is not intuitive, I'd say, but given that there is no indication of > where this statement came from or whose idea it follows, it's unclear > how to evaluate that. FYI, I was totally confused by this also when researching this for the PG 12 release notes. I am glad we are going to redo it for PG 13. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Commits
-
Revert "Add DECLARE STATEMENT support to ECPG."
- 08e04a5f99d5 12.0 landed
- 96b6c82c9dd4 13.0 landed