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: Bug in DatabaseMetaData.getColumns() with columns based on domains
Date: 2010-10-21 12:57:03
Message-ID: i9pdb3$6t5$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2010-10-21 17:49:24 Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous Message Michael musset 2010-10-21 08:26:17 Fwd: JDBC4 with SQLXML and postgresql-8.4-702.jdbc4.jar