Re: Bug in DatabaseMetaData.getColumns() with columns based on domains - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
Date
Msg-id alpine.BSO.2.00.1010230331180.30080@leary.csoft.net
Whole thread Raw
In response to Re: Bug in DatabaseMetaData.getColumns() with columns based on domains  (dmp <danap@ttc-cmc.net>)
Responses Re: Bug in DatabaseMetaData.getColumns() with columns based on domains  (dmp <danap@ttc-cmc.net>)
Re: Bug in DatabaseMetaData.getColumns() with columns based on domains  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-jdbc

On Thu, 21 Oct 2010, dmp wrote:

> The early attached file query for the column's information was from the
> information_schema.columns table and does show the correct result for the
> salary field IS_NULLABLE.
>

Thanks for the hint.  Doing the same thing that the information_schema
does was pretty easy.  I've fixed this in CVS and I've also adjusted
ResultSetMetaData.isNullable to have the same behavior.  I've backpatched
this to 8.4 because that's as far as was easy.

Here's a jar you can test with:

http://ejurka.com/pgsql/jars/domnn/

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: JDBC4 with SQLXML and postgresql-8.4-702.jdbc4.jar
Next
From: Michael musset
Date:
Subject: Re: JDBC4 with SQLXML and postgresql-8.4-702.jdbc4.jar