X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EEF67D1B18F; Wed, 19 May 2004 21:33:56 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 90400-02; Wed, 19 May 2004 21:33:38 -0300 (ADT) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 01183D1B188; Wed, 19 May 2004 21:33:34 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i4K0XMT28270; Wed, 19 May 2004 20:33:22 -0400 (EDT) From: Bruce Momjian Message-Id: <200405200033.i4K0XMT28270@candle.pha.pa.us> Subject: Re: Bug in translation of DEALLOCATE PREPARE In-Reply-To: <406E4D31.7070200@k2defender.com> To: Adriaan Joubert Date: Wed, 19 May 2004 20:33:22 -0400 (EDT) Cc: pgsql-interfaces@postgresql.org, meskes@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.5 tagged_above=0.0 required=5.0 tests=WEIRD_QUOTING X-Spam-Level: X-Archive-Number: 200405/21 X-Sequence-Number: 4913 Michael, would you comment on this? Thanks. --------------------------------------------------------------------------- Adriaan Joubert wrote: > > [Apologies if you see multiple of these - this is my 4th attempt to post > in 3 days.] > > Hi, > > I believe in recent interface changes changes in ecpg the > translation of 'DEALLOCATE PREPARE' were missed out. This worker fine > under 7.3.5. > > Currently > > EXEC SQL DEALLOCATE PREPARE foobar; > > is translated to > > { ECPGdeallocate(__LINE__, ""foobar"");} > > The double quotes are obviously wrong, but when I remove them the > compiler says that it now expects 3 arguments to ECPGdeallocate instead > of 2. I assume this is a trivial fix to ecpg, but I don't have the time > right now to try to understand what ecpg does internally. I'd really > appreciate it if somebody could tell me how/where ecpg needs to be fixed. > > Cheers, > > Adriaan > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073