From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <dpage(at)vale-housing(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: Roadmap for FE/BE protocol redesign |
Date: | 2003-03-11 09:34:33 |
Message-ID: | 50149.80.177.99.193.1047375273.squirrel@ssl.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
It's rumoured that Bruce Momjian once said:
> Tom Lane wrote:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2003-03-11 10:07:07 | Re: Roadmap for FE/BE protocol redesign |
Previous Message | Dave Page | 2003-03-11 09:25:07 | Re: Roadmap for FE/BE protocol redesign |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2003-03-11 10:07:07 | Re: Roadmap for FE/BE protocol redesign |
Previous Message | Dave Page | 2003-03-11 09:25:07 | Re: Roadmap for FE/BE protocol redesign |