Re: Problem with getImportedKeys / getExportedKeys

From: "Vianen, Jeroen van" <jeroen(dot)van(dot)vianen(at)satama(dot)com>
To: "'Jason Davies '" <jason(at)netspade(dot)com>
Cc: "'PostgreSQL JDBC '" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Problem with getImportedKeys / getExportedKeys
Date: 2002-01-16 19:06:55
Message-ID: F9926D32A30ED511B8E30050044AB52E10152F@ams010.satama.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Jason,

Thanks for the patch. I will try it out soon.

Regarding the case sensitivity, I think this is an issue that needs to be
resolved in many more places in JDBC (if at all).

Thanks,

Jeroen

-----Original Message-----
From: Jason Davies
To: Vianen, Jeroen van
Cc: PostgreSQL JDBC
Sent: 15-1-02 21:26
Subject: Re: [JDBC] Problem with getImportedKeys / getExportedKeys

Yes, at the moment they are the wrong way round because of a
misinterpretation on my part. Easily fixed, by changing the SQL part so
that the Java code reads:

...

+ ((primaryTable != null) ? "AND c.relname='" + primaryTable + "' " :
"")
+ ((foreignTable != null) ? "AND c2.relname='" + foreignTable + "' " :
"")

...

I've attached a patch for this for now. But maybe case-sensitive stuff
needs to be resolved?

Thanks,
Jason Davies

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Barry Lind 2002-01-17 04:23:44 Re: setBoolean and char/varchar
Previous Message Paulo Merson 2002-01-16 16:52:33 setBoolean and char/varchar