Re: [BUGS] JDBC getImortedKeys() getExportedKeys() incorrect ON - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: [BUGS] JDBC getImortedKeys() getExportedKeys() incorrect ON
Date
Msg-id Pine.LNX.4.33.0311030522150.29431-300000@leary.csoft.net
Whole thread Raw
Responses Re: [BUGS] JDBC getImortedKeys() getExportedKeys()  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc

On Fri, 15 Aug 2003, Richard Froud wrote:

> Please enter a FULL description of your problem:
> ------------------------------------------------
> When reading database metadata for foreign keys using the JDBC
> DatabaseMetaData.getImportedKeys() and DatabaseMetaData.getExportedKeys()
> methods the ON UPDATE rule is returned as the ON DELETE rule.  It is also
> correctly returned as the ON UPDATE rule.  Therefore there is no way to
> access the ON DELETE rule.  Consequenntly innaccurate representations of the
> database structure are obtained.

Here is a patch for this.  Additionally the on delete rule would not
return importedKeyRestrict because of a missing if statement.  Also an
addition to the test suite is attached.

Kris Jurka


Attachment

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: [BUGS] Bug #886: jdbc "update row" can mess up other columns
Next
From: Kris Jurka
Date:
Subject: Re: Driver.acceptsURL(String) not working correctly