From: | Dave Cramer <dave(at)fastcrypt(dot)com> |
---|---|
To: | "pgsql-interfaces(at)postgresql(dot)org" <pgsql-interfaces(at)postgresql(dot)org> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | qualified column names |
Date: | 2003-04-17 15:19:26 |
Message-ID: | 1050592766.6918.33.camel@inspiron.cramers |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-interfaces pgsql-jdbc |
I didn't get a reply to this, I'm wondering if it just slipped through the cracks?
jdbc and I suspect odbc have a requirement to return the table, and
schema of a column in a result set.
for jdbc at least a possible solution is to return
schema.table.column for each column returned. This could be turned
off/on using GUC variable.
functions, and computed fields can just return the column name as they
don't belong to a schema or table.
Does anyone have any other requirments?
--
Dave Cramer <dave(at)fastcrypt(dot)com>
Cramer Consulting
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff MacDonald | 2003-04-17 15:24:42 | ran an update outside of transaction, can i roll it back in anyway ? |
Previous Message | Tom Lane | 2003-04-17 14:43:59 | Re: Executing queries in C functions |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-04-17 15:26:20 | Re: [pgadmin-hackers] pg_clog woes with 7.3.2 - Episode 2 |
Previous Message | Tom Lane | 2003-04-17 14:35:31 | Re: For the ametures. (related to "Are we losing momentum?") |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Gamache | 2003-04-18 08:29:03 | DBD::Pg large processor load. |
Previous Message | Mathieu Arnold | 2003-04-17 14:47:37 | DBD::PgSPI |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-04-17 17:41:21 | Re: [PATCHES] the build |
Previous Message | Nic Ferrier | 2003-04-17 09:21:48 | Re: [PATCHES] the build |