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

Re: Support for DatabaseMetadata: getCatalogName, getTableName,

From: Ken Johanson <pg-user(at)kensystem(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Support for DatabaseMetadata: getCatalogName, getTableName,
Date: 2007-01-08 17:15:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Kris Jurka wrote:
> What we get now in the V3 protocol:
> 1) the column name which may be an alias but we don't know if it came 
> from an alias or not, consider SELECT a AS a.  If we get "a" we don't 
> know if it was aliased or not.
> 2) The underlying table's oid which can be used to lookup it's name and 
> schema.
> 3) The underlying column's number in the table which can be used to 
> lookup its name.
> No information on a table alias is available.
>> If so, does anyone know off hand if V3 is somehow extensible; i.e can 
>> we add in metadata without breaking apps or major version?
> No the RowDescription message is fixed:

Kris, do you know roughly when a v4 protocol could be on the radar?.. is 
it months out (or years?), or has it even been discussed yet? I'm trying 
to decide if I should vote-in on having this info added into that 
version, if there is a discussion/planning thread somewhere...

Thx, ken

In response to


pgsql-jdbc by date

Next:From: Ken JohansonDate: 2007-01-08 17:18:07
Subject: Re: Synthesize support for Statement.getGeneratedKeys()?
Previous:From: claudio ferrazDate: 2007-01-08 17:06:41
Subject: How to recoup the messages on the execution of a query while the query is running ,using java(JDBC)?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group