From: Dave Page <dpage@vale-housing.co.uk>
To: pgman@candle.pha.pa.us
Cc: tgl@sss.pgh.pa.us
Cc: dpage@vale-housing.co.uk
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Tue, 11 Mar 2003 09:34:33 -0000 (GMT)
Message-ID: <50149.80.177.99.193.1047375273.squirrel@ssl.vale-housing.co.uk> (raw)
In-Reply-To: <200303110244.h2B2i1j15763@candle.pha.pa.us>
References: <1942.1047350265@sss.pgh.pa.us>
<200303110244.h2B2i1j15763@candle.pha.pa.us>
It's rumoured that Bruce Momjian once said:
> Tom Lane wrote:
>> Bruce Momjian <pgman@candle.pha.pa.us> 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.
> :-)
Well, what would constitute a complete spec? I think I've told the group
what I would like to be able to do, what unanswered questions can I
(hopefully :-) ) answer?
Regards, Dave.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: dpage@vale-housing.co.uk, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <50149.80.177.99.193.1047375273.squirrel@ssl.vale-housing.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox