Re: Support for DatabaseMetadata: getCatalogName, getTableName, - Mailing list pgsql-jdbc

From Ken Johanson
Subject Re: Support for DatabaseMetadata: getCatalogName, getTableName,
Date
Msg-id 45A27C36.7060805@kensystem.com
Whole thread Raw
In response to Re: Support for DatabaseMetadata: getCatalogName, getTableName,  (Kris Jurka <books@ejurka.com>)
Responses Re: Support for DatabaseMetadata: getCatalogName, getTableName,
List 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:
>
> http://www.postgresql.org/docs/current/static/protocol-message-formats.html
>


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



pgsql-jdbc by date:

Previous
From: "claudio ferraz"
Date:
Subject: How to recoup the messages on the execution of a query while the query is running ,using java(JDBC)?
Next
From: Ken Johanson
Date:
Subject: Re: Synthesize support for Statement.getGeneratedKeys()?