X-Original-To: pgsql-hackers@postgresql.org Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 58E8F4760E3; Mon, 10 Mar 2003 21:44:13 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h2B2i1j15763; Mon, 10 Mar 2003 21:44:01 -0500 (EST) From: Bruce Momjian Message-Id: <200303110244.h2B2i1j15763@candle.pha.pa.us> Subject: Re: Roadmap for FE/BE protocol redesign In-Reply-To: <1942.1047350265@sss.pgh.pa.us> To: Tom Lane Date: Mon, 10 Mar 2003 21:44:01 -0500 (EST) Cc: Dave Page , pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200303/407 X-Sequence-Number: 36653 Tom Lane wrote: > Bruce Momjian writes: > > I was willing to add a hack to enable default column labels to be > > "table.column" --- that seemed like the least obtrusive. > > Most of the definitional issues still apply: which table name are you > going to insert, and under what conditions? > > If we're revising the protocol, there's no reason to hack up the column > label to carry two pieces of info; it'd be cleaner to provide a separate > slot in the T message to carry the table name. I just want to see a > reasonably complete spec for what the feature is supposed to do, before > we buy into it ... I don't think we can get a complete spec, and hence the _hack_ idea. :-) -- 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