Re: Problem with getImportedKeys / getExportedKeys - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Problem with getImportedKeys / getExportedKeys
Date
Msg-id 013001c1a024$d7106fd0$c201a8c0@inspiron
Whole thread Raw
In response to Re: Problem with getImportedKeys / getExportedKeys  (Justin Clift <justin@postgresql.org>)
Responses Re: Problem with getImportedKeys / getExportedKeys
List pgsql-jdbc
I will try to patch this sometime today

DAve

-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Justin Clift
Sent: Friday, January 18, 2002 4:38 AM
To: Bruce Momjian
Cc: Jason Davies; Jeroen van Vianen; PostgreSQL JDBC
Subject: Re: [JDBC] Problem with getImportedKeys / getExportedKeys


Hi Bruce,

Can we get this tested and committed before RC1 is released?

All of the Database Admin/Management tools out there which use JDBC and
support RI need this in order to work correctly.

Making a point of it as I think it's pretty important.

:-)

Regards and best wishes,

Justin Clift


Jason Davies wrote:
>
> Hi,
>
> I've fixed it completely now (I think) - it took more changes than I
> thought would be necessary. Here is a new patch (against current CVS).

> Once it has been tested it should be commited to CVS as it is quite an

> important fix.
>
> This patch makes getImportedKeys() and getExportedKeys() report the
> correct relationships (they were the wrong way round before) and
> correct number of keys.
>
> Thanks,
> Jason Davies
>
> On Thu, Jan 17, 2002 at 08:00:48PM +0100, Jeroen van Vianen wrote:
> > Hi Jason,
> >
> > At 20:06 01-16-2002 +0100, Vianen, Jeroen van wrote:
> > >Thanks for the patch. I will try it out soon.
> >
> > I've tried your patch and the output is as follows:
> >
> > java -classpath .:postgresql.jar TestKeys users
> > Imported keys:
> > Exported keys:
> > PKTABLE_NAME = users_roles
> > PKCOLUMN_NAME = userid
> > FKTABLE_NAME = users
> > FKCOLUMN_NAME = userid
> >
> > # java -classpath .:postgresql.jar TestKeys users_roles Imported
> > keys: PKTABLE_NAME = users_roles
> > PKCOLUMN_NAME = userid
> > FKTABLE_NAME = users
> > FKCOLUMN_NAME = userid
> > PKTABLE_NAME = users_roles
> > PKCOLUMN_NAME = userid
> > FKTABLE_NAME = users
> > FKCOLUMN_NAME = userid
> > Exported keys:
> >
> > Comparing this with Oracle's output I noticed that all PK* and FK*
> > columns have been exchanged and that the two imported keys for table

> > users_roles are the same. Oracle correctly reports a key from
> > users_roles to users and from users_roles to roles.
> >
> > Any clue?
> >
> >
> > Jeroen
> >
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
>
> --
> Jason Davies
>
> jason@netspade.com
>
>
> ----------------------------------------------------------------------
> --
>
>    DatabaseMetaData.java.diffName: DatabaseMetaData.java.diff
>                              Type: Plain Text (text/plain)
>
>
> ----------------------------------------------------------------------
> --
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
majordomo@postgresql.org)

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org



pgsql-jdbc by date:

Previous
From: Rolf Heckendorn
Date:
Subject: Unicode transformation for Mac OS X
Next
From: Bruce Momjian
Date:
Subject: Re: Problem with getImportedKeys / getExportedKeys