Bug #571: Impossible to completly support JDBC - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #571: Impossible to completly support JDBC
Date
Msg-id 200202031924.g13JO6o23388@postgresql.org
Whole thread Raw
List pgsql-bugs
Tiago Antao (tiagoantao@yahoo.com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Impossible to completly support JDBC

Long Description
This is in fact to report 2 problems regarding JDBC.

#1: JDBC DatabaseMetaData.getImportedKeys returns a null because it was not implemented. I think the correct behaviour
wouldbe to raise a SQLException. If there is an agreement on this, I would gladly implement the (simple) solution. 

#2: This is much more serious: It is impossible, AFAIK, to get foreign key information from the metadata tables pg_* on
PostgreSQL.As I understand the fkeys are implemented via triggers... but it would be interesting that fk info would be
madeavailable as metadata. 
Without this I believe it is _impossible_ to have a fully compliant JDBC driver.

Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Eric Scroger
Date:
Subject: JDBC- SQLException results returned?
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #572: Double Format