Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9WnA-0005JK-UZ for pgsql-bugs@arkaria.postgresql.org; Sat, 22 Aug 2020 16:54:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k9Wn9-0008IL-9Y for pgsql-bugs@arkaria.postgresql.org; Sat, 22 Aug 2020 16:54:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9Wn9-0008ID-3K for pgsql-bugs@lists.postgresql.org; Sat, 22 Aug 2020 16:54:55 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9Wn2-0004ep-0o; Sat, 22 Aug 2020 16:54:54 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1k9Wn0-0005Pg-A1; Sat, 22 Aug 2020 12:54:46 -0400 Date: Sat, 22 Aug 2020 12:54:46 -0400 From: Bruce Momjian To: Michael Meskes Cc: egashira.yusuke@jp.fujitsu.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16547: ECPG can't CALL the procedure which has INOUT parameter Message-ID: <20200822165446.GC26781@momjian.us> References: <16547-0d8cd56ecb46f943@postgresql.org> <20200822005954.GP13363@momjian.us> <203b64f3ec14fcfec8d31fe3646f9037ad97b713.camel@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <203b64f3ec14fcfec8d31fe3646f9037ad97b713.camel@postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, Aug 22, 2020 at 05:52:23PM +0200, Michael Meskes wrote: > > > ... > > > Also, I found the patch[1] introducing "INTO" clause in CALL of > > > ECPG. > > > However, the patch changes the EXC SQL CALL statement to always > > > require INTO > > > clause. > > > > > > [1] > > > https://www.postgresql.org/message-id/CAE9k0P%3DGQFjfy9jHCPDw4Eh_xE%3DNw%3D9y4f-CuTZp1L%2B6vEHwFg%40mail.gmail.com > > > > This looks like something we should either fix or document. Michael > > Meskes, do you have an opinion? > > Yes, I think it should definitely be fixed. In fact I was looking into > it and iirc the patch mentioned had a couple issues but could be a good > base for the fix. Unfortunately I have not found the time yet to take > care of it. > > So in short, hopefully we can fix it shortly. Thank you. I am glad you are aware of it. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee