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

From Dave Cramer
Subject Re: [BUGS] JDBC getImortedKeys() getExportedKeys()
Date
Msg-id 1067873079.1622.69.camel@localhost.localdomain
Whole thread Raw
In response to Re: [BUGS] JDBC getImortedKeys() getExportedKeys() incorrect ON  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Patch Applied,

Thanks,

Dave
On Mon, 2003-11-03 at 05:25, Kris Jurka wrote:
> 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
>
>
> ______________________________________________________________________
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings


pgsql-jdbc by date:

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