Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.8.8/8.7.5) with ESMTP id TAA29049; Sun, 26 Apr 1998 19:09:40 -0400 (EDT) Received: (from maillist@localhost) by candle.pha.pa.us (8.8.5/8.8.5) id SAA05889; Sun, 26 Apr 1998 18:55:09 -0400 (EDT) From: Bruce Momjian Message-Id: <199804262255.SAA05889@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size To: maillist@candle.pha.pa.us (Bruce Momjian) Date: Sun, 26 Apr 1998 18:55:09 -0400 (EDT) Cc: tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org In-Reply-To: <199804262138.RAA04996@candle.pha.pa.us> from "Bruce Momjian" at Apr 26, 98 05:38:31 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > One thing that likely would *not* work very nicely is copy in/out > > as part of a multi-command query, since there is currently no provision > > for PQendcopy to return result(s). This is pretty braindead IMHO, > > but I'm not sure we can change PQendcopy's API. Any thoughts? What Adding a return result to PQendcopy would not be a big deal. Just document it so the few people who do this in application know to free the result. The interface libraries can handle the change. -- Bruce Momjian | 830 Blythe Avenue maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026 + If your life is a hard drive, | (610) 353-9879(w) + Christ can be your backup. | (610) 853-3000(h)