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 1kUvM8-0002uN-IR for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Oct 2020 17:23:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kUvM7-0005Pb-Fj for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Oct 2020 17:23:27 +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 1kUvM7-0005PU-9m for pgsql-bugs@lists.postgresql.org; Tue, 20 Oct 2020 17:23:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kUvM0-0003Ul-TM for pgsql-bugs@lists.postgresql.org; Tue, 20 Oct 2020 17:23:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09KHNInd652859; Tue, 20 Oct 2020 13:23:18 -0400 From: Tom Lane To: 1250kv <1250kv@gmail.com> cc: pgsql-bugs@lists.postgresql.org Subject: Re: ECPG bug: "unterminated quoted identifier" In-reply-to: References: Comments: In-reply-to 1250kv <1250kv@gmail.com> message dated "Tue, 20 Oct 2020 19:25:36 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <652857.1603214598.1@sss.pgh.pa.us> Date: Tue, 20 Oct 2020 13:23:18 -0400 Message-ID: <652858.1603214598@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 1250kv <1250kv@gmail.com> writes: > void main() > { > char *foo = "aaa\"bbb"; > EXEC SQL char *bar = "aaa\"bbb"; > } > ecpg sample.pgc -o 1.c > sample .pgc:10: ERROR: unterminated quoted identifier I don't really see a bug there. While I'm not an ecpg expert by any means, I'd expect the EXEC SQL section to parse quoted strings according to SQL rules not C rules. And under SQL, that's not what you do to write a valid quoted identifier. regards, tom lane