| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Reggie Burnett <rykr(at)bellsouth(dot)net> |
| Cc: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 'Dave Cramer' <dave(at)fastcrypt(dot)com>, 'PostgreSQL Hackers Mailing List' <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Request for qualified column names |
| Date: | 2003-01-29 05:46:42 |
| Message-ID: | 1043819202.15575.6.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2003-01-27 at 10:44, Reggie Burnett wrote:
> Well, certainly the driver could parse the sql and extract what it
> thinks is the table name. It just seems quite foreign to me to have a
> database engine go through the motions of determining column location
> and have ready access to all the metadata for all the columns in a
> resultset and then intentionally leave all that out of the FE/BE.
I think the issue is that no one has yet proposed a consistent set of
behaviour for this feature, particularly in the cases that Tom raised.
If you would like this feature, I'd suggest that you outline some
behaviour that everyone can agree upon.
Griping about "intentionally left out" features when the feature itself
is not even well defined doesn't strike me as very productive.
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-01-29 06:12:01 | Re: New buildin function |
| Previous Message | Curt Sampson | 2003-01-29 05:44:34 | Specifying Rowtypes |