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 i9q5p6$lcb$1@dough.gmane.org
Whole thread Raw
In response to Re: Bug in DatabaseMetaData.getColumns() with columns based on domains  (dmp <danap@ttc-cmc.net>)
List pgsql-jdbc
dmp wrote on 21.10.2010 19:57:
>> 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.
>>
> 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.

Sorry, you are right I should have mentioned that.

I tried it with the exact same version as you (PG 9.0.1 and JDBC 9.0-801)

Regards
Thomas

pgsql-jdbc by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Support for JDBC setQueryTimeout, et al.
Next
From: Thomas Kellerer
Date:
Subject: Re: Bug in DatabaseMetaData.getColumns() with columns based on domains