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-21 20:20:10
Message-ID: i9q79p$sp1$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message dmp 2010-10-22 01:25:36 Re: Bug in DatabaseMetaData.getColumns() with columns based on domains
Previous Message Thomas Kellerer 2010-10-21 19:54:14 Re: Bug in DatabaseMetaData.getColumns() with columns based on domains