Re: BUG #1656: ResultSetMetaData.getColumnDisplaySize()

From: Kris Jurka <books(at)ejurka(dot)com>
To: Sergio Lob <sergio_lob(at)iwaysoftware(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1656: ResultSetMetaData.getColumnDisplaySize()
Date: 2005-05-10 19:33:45
Message-ID: Pine.BSO.4.56.0505101428500.25696@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 10 May 2005, Sergio Lob wrote:

> Bug reference: 1656
> PostgreSQL version: 8.0.1
> Description: ResultSetMetaData.getColumnDisplaySize() returns value
> -1
> Details:
>
> ResultSetMetaData.getColumnDisplaySize() returns value -1 for several
> columns of answer set generated by DatabaseMetaData.getTables() method.

ResultSetMetaData.getColumnDisplaySize() returns -1 for any column that
has an unknown size. Consider the REMARKS column of getTables(). This
data comes from the system's pg_description.description column which is of
type "text". There is no defined length for this, so we have decided to
return -1.

> Additionally, I don't understand why the data type of column 1 is described
> as "OTHER", as opposed to all the other columns, which are of type "VARCHAR"
> (attained through ResultSetMetaData.getColumnType() method).
>

TABLE_CAT is generated by an untyped "SELECT NULL", we should probably
cast this to name, or report the currently connected database name here.

Kris Jurka

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2005-05-11 03:25:33 Re: BUG #1578: ::bit(n) behaves "differently" if applied to bit
Previous Message Marcio Roberto Chiaveli 2005-05-10 18:08:18 BUG #1658: Error download of odbc