Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Wrong column names in ResultSetMetaData


  • From: Kris Jurka <books(at)ejurka(dot)com>
  • To: Mike Martin <mmartin(at)vieo(dot)com>
  • Cc: pgsql-jdbc(at)postgresql(dot)org
  • Subject: Re: Wrong column names in ResultSetMetaData
  • Date: Thu, 29 Jul 2004 16:41:49 -0500 (EST)
  • Message-id: <Pine.BSO.4.56.0407291637280.9570@leary.csoft.net> <text/plain>


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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group