X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 723349DD617; Mon, 6 Feb 2006 16:40:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 40353-10; Mon, 6 Feb 2006 16:40:17 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 54EB29DD614; Mon, 6 Feb 2006 16:40:13 -0400 (AST) Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by svr4.postgresql.org (Postfix) with ESMTP id 09C485AF08A; Mon, 6 Feb 2006 20:40:14 +0000 (GMT) Received: from feivel (unknown [88.128.29.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 71AB1D75FC; Mon, 6 Feb 2006 21:40:04 +0100 (CET) Received: by feivel (Postfix, from userid 1000) id E78514BFCE; Mon, 6 Feb 2006 21:33:16 +0100 (CET) Date: Mon, 6 Feb 2006 21:33:16 +0100 From: Michael Meskes To: Bruce Momjian Cc: andrew5@ece.cmu.edu, PostgreSQL-patches , PostgreSQL-interfaces Subject: Re: [BUGS] BUG #2171: Differences compiling plpgsql in ecpg and psql Message-ID: <20060206203316.GA9025@1> Mail-Followup-To: Bruce Momjian , andrew5@ece.cmu.edu, PostgreSQL-patches , PostgreSQL-interfaces References: <20060114225417.5885DF0A7F@svr2.postgresql.org> <200602020448.k124mjG25834@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602020448.k124mjG25834@candle.pha.pa.us> User-Agent: Mutt/1.5.11+cvs20060126 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200602/14 X-Sequence-Number: 5978 On Wed, Feb 01, 2006 at 11:48:45PM -0500, Bruce Momjian wrote: > I have researched your report, and you are right, there are two ecpg > bugs here. First, dollar quoting uses single-quotes internally to do > the quoting, but it does not double any single-quotes in the > dollar-quoted string. Actually ecpg should not translate dollar quoting at all. I'm going to fix this. Dollar quotes will then be send to the backend with translation and the backend takes care of the rest. > Second, when a dollar quoted string or single-quoted string spans > multiple lines, ecpg does not escape the newline that is part of the > string. Some compilers will accept an unescaped newline in a string, > while others will not: Not sure, but there appears to be a bug in the routine that outputs a statement. I will change that one as well and would ask you to just check again. It seems to me that this also fixes your problem. I tried with the one test case in this email and it seems to work. But then I'm currently travelling and do not have that much spare time to test. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!