Re: Wrong column names in ResultSetMetaData - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Wrong column names in ResultSetMetaData
Date
Msg-id Pine.BSO.4.56.0407291637280.9570@leary.csoft.net
Whole thread Raw
In response to Re: Wrong column names in ResultSetMetaData  ("Mike Martin" <mmartin@vieo.com>)
List pgsql-jdbc

On Thu, 29 Jul 2004, Mike Martin wrote:

> 2.  Every other JDBC driver I'm familiar with behaves that way
>     (with the exception, I hear, of MimerSQL, which confuses
>     getColumnLabel() with SQL alias the way our new code does).

What do they return for getColumnLabel()?  Previously we returned the same
value for both methods simply because we couldn't implement getColumnName
as we do now.  If they all return the alias in getColumnLabel that would
be telling.

> I'm not clear why a JDBC client would want or need to know the
> "underlying" column name, if there even is one.  I can see why
> the driver might need to know that internally for purposes of
> updateability but that's something different.
>

To allow client software to do the updates or allow the user to navigate
from a query result column to the base table or to/through foreign keys on
it.  There could be a number of uses.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Bug in 7.4_213 driver: returns VARCHAR instead of
Next
From: Kris Jurka
Date:
Subject: Re: Bug in 7.4_213 driver: returns VARCHAR instead of