Re: [HACKERS] Roadmap for FE/BE protocol redesign
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] Roadmap for FE/BE protocol redesign |
Дата | |
Msg-id | 200303110227.h2B2R6n14056@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Roadmap for FE/BE protocol redesign (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Roadmap for FE/BE protocol redesign
|
Список | pgsql-interfaces |
Tom Lane wrote: > "Dave Page" <dpage@vale-housing.co.uk> writes: > > What about the addition of pg_attribute.attrelid & > > pg_attribute.attname/attnum in RowDesription messages to identify the > > underlying attribute (where appropriate)? > > Well, we can talk about it, but I still think that any frontend that > relies on such information is broken by design. (And if that means the > JDBC spec is broken, then the JDBC spec is broken.) > > Just to start with, if I do "SELECT * FROM view", am I going to see the > info associated with the view column, or with the hypothetical > underlying table column? (Actually, didn't I already make a list of a > bunch of ways in which this concept is underspecified? AFAIR, you > didn't suggest answers to any of those questions ... but we need answers > to all of them if we are going to implement the feature.) I was willing to add a hack to enable default column labels to be "table.column" --- that seemed like the least obtrusive. -- 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, Pennsylvania19073
В списке pgsql-interfaces по дате отправления: