Skip site navigation (1) Skip section navigation (2)

Re: Bug in DatabaseMetaData.getColumns() with columns based on domains

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
Date: 2010-10-23 15:49:45
Message-ID: i9v06o$gk$1@dough.gmane.org (view raw or flat)
Thread:
Lists: 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 the same domains in different schemas...

Regards
Thomas


In response to

pgsql-jdbc by date

Next:From: Robert WimmerDate: 2010-10-24 00:11:24
Subject:
Previous:From: dmpDate: 2010-10-23 15:30:34
Subject: Re: Bug in DatabaseMetaData.getColumns() with columns based on domains

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group