From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ken Johanson <pg-user(at)kensystem(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel |
Date: | 2006-12-29 16:15:57 |
Message-ID: | 674F8180-BA35-4CBA-9A4E-2A8EBDE0B095@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I stand corrected. I'll try to find some time this week to work on
some of the outstanding issues.
Tom, as of which version has this been implemented ?
Dave
On 29-Dec-06, at 10:47 AM, Tom Lane wrote:
> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> The backend does not provide us with this information, so it is not
>> trivial to implement( or even possible in some cases) .
>
> Huh? We added table oid and column number to the RowDescription
> message
> specifically to support those JDBC methods. You would have to
> incur an
> additional round trip to the server to get names from these numbers,
> but it's certainly implementable ... and I thought it'd been
> implemented
> long ago, so I'm a bit surprised by Ken's report.
>
> As for getCatalogName, I think just returning the database name (which
> you should still have from the connection request) would meet the
> spec.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-29 16:21:29 | Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel |
Previous Message | Tom Lane | 2006-12-29 15:47:02 | Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel |