I am just seeing this message now. Does this patch need to be backed out?
>
> I don't like this patch. Nothing wrong with the code, but with what is
> being done. I wouldn't expect the setCatalog method to end my current
> transaction and quietly reconect me to another database. In this n
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
>
> This patch merges the identical methods from the JDBC1 and JDBC2
> connection implementations (org.postgresql.jdbc[1|2]
Brian,
Make sure the jar is in the classpath on the server
Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Yaochiu Huang
Sent: July 17, 2001 9:46 PM
To: [EMAIL PROTECTED]
Subject: [JDBC] Help! Driver cannot be loaded.
Dear Sir or Madam,
I got a
Dear Sir or Madam,
I got an error as per subject. Following is my
configurations:
Server: Red Hat Linux 7.1
PostgreSQL: 7.1.2
JDBC Driver: jdbc7.1-1.2.jar
IP: 192.168.0.1
Client: Windows 98
JDBC Driver:
first time: jdbc7.1-1.2.jar
second time: jdbc7.1-1.3.jar
IP: 192.168.0.3
Driver:
I don't like this patch. Nothing wrong with the code, but with what is
being done. I wouldn't expect the setCatalog method to end my current
transaction and quietly reconect me to another database. In this new
connection my auto comit status will be reset and there could be other
side effe
