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 i9q79p$sp1$1@dough.gmane.org
Whole thread Raw
In response to Bug in DatabaseMetaData.getColumns() with columns based on domains  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
List pgsql-jdbc
Thomas Kellerer wrote on 21.10.2010 14:57:
> Hi,
>
> consider the following table and domain:
>
> CREATE DOMAIN salary_domain AS numeric(12,2) NOT NULL CHECK (value > 0);
> CREATE TABLE employee (id integer not null, salary salary_domain);
>
> DatabaseMetaData.getColumns(null, "public", "employee", "%");
>
> returns "YES" for the column IS_NULLABLE in the ResultSet whereas it should flag that column as not nullable.
>

OK, I realized that not even psql or pgAdmin will display such a column as "not null"
So it is not a JDBC driver issue (but rather a PostgreSQL "core" issue)

Sorry for the noise
Thomas

pgsql-jdbc by date:

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