Re: ResultSetMetaData enhancements

From: Kris Jurka <books(at)ejurka(dot)com>
To: snpe <snpe(at)snpe(dot)co(dot)yu>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: ResultSetMetaData enhancements
Date: 2003-12-31 17:08:15
Message-ID: Pine.LNX.4.33.0312311206410.17433-100000@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 31 Dec 2003, snpe wrote:

> Hello,
> Is it in cvs (7.4, head ) ?

No. I don't think it will go into 7.4 as it is a new feature and I don't
think anything will go into HEAD until the cvs repository is moved to
gborg.

Kris Jurka

>
> On Tuesday 30 December 2003 10:01 am, Kris Jurka wrote:
> > This patch is the culmination of Jan-Andre's work on enhancing the
> > ResultSetMetaData methods with new information available in the V3
> > protocol. He wandered off of the verge of completing it and I've just
> > done some minor reworking and editing.
> >
> > This implements getSchemaName, getTableName, getColumnName,
> > getColumnLabel, and isNullable.
> >
> > Kris Jurka
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Tenny 2003-12-31 18:50:36 Portable interpretation of jdbc SQLException for SERIALIZABLE transaction restart?
Previous Message snpe 2003-12-31 16:27:16 Re: ResultSetMetaData enhancements