Re: [INTERFACES] sigh .. another bug in the JDBC driver (ResultSetMetaData.getColumnDisplaySize)

From: Hannu Krosing <hannu(at)trust(dot)ee>
To: "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu>
Cc: jens(at)jens(dot)de, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] sigh .. another bug in the JDBC driver (ResultSetMetaData.getColumnDisplaySize)
Date: 1999-08-03 07:43:16
Message-ID: 37A69D94.330E098A@trust.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

"Ross J. Reedstrom" wrote:
>
> On Mon, Aug 02, 1999 at 07:23:07PM +0000, Jens Glaser wrote:
> > Hi,
> >
> > here's just another annoying bug in the JDBC driver:
> >
> > ResultSetMetaData.getColumnDisplaySize() returns the length of the
> > *column label*, but it is expected to return the max width of the column!
> >
>
> Hmm, the Zope Python interface suffers from the same problem (and the
> same work around): lack of column width info, substituting the column
> label length.

I'm not sure that this info is available through libpq but it appeared
at
least to protocol level in about 6.4 for variable length fields (it has
always been there for fixed width of course). At least ODBC drivers do
use it.

-------
Hannu

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message John Ridout 1999-08-03 09:03:37 RE:
Previous Message Thomas Lockhart 1999-08-03 04:19:57 Re: [INTERFACES] PGACCESS documentation