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

Thomas Kellerer wrote:
> 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
>
>
Perhaps you could provide the Database and JDBC versions to help those that
will need to review the report. I have confirmed on PostgreSQL 9.0.1 and
JDBC postgresql-9.0-801.jdbc3.

Output:

Connection Created
SELECT * FROM "public"."employee" LIMIT 1
Column Name: id IS_NULLABLE: NO
Column Name: salary IS_NULLABLE: YES
Connection Closed

Attached files needed to setup test case and other reviewed data.

danap.