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

From Thomas Kellerer
Subject Bug in DatabaseMetaData.getColumns() with columns based on domains
Date
Msg-id i9pdb3$6t5$1@dough.gmane.org
Whole thread Raw
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
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.

Regards
Thomas

pgsql-jdbc by date:

Previous
From: Michael musset
Date:
Subject: Fwd: JDBC4 with SQLXML and postgresql-8.4-702.jdbc4.jar
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Support for JDBC setQueryTimeout, et al.