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

From Thomas Kellerer
Subject Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
Date
Msg-id i9v06o$gk$1@dough.gmane.org
Whole thread Raw
In response to Re: Bug in DatabaseMetaData.getColumns() with columns based on domains  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Kris Jurka wrote on 23.10.2010 09:37:
> 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/
>

Thanks for the quick reaction. I didn't expect this to be a client-side only problem (including psql ;)
With my little example, the nullable attribute is displayed correctly with your version of the driver.

Could you also look into the values reported for the TYPE_NAME in getColumns() for domains?

I posted a bug reported that the domain's name is not fully qualified so that it's impossible to distinguish between
thesame domains in different schemas... 

Regards
Thomas

pgsql-jdbc by date:

Previous
From: dmp
Date:
Subject: Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
Next
From: Robert Wimmer
Date:
Subject: