On Wed, 1 Aug 2001 19:40:06 -0700, you wrote:
>I get 100+ errors building. Many of the messages are complaining
>that they cannot find javax.transaction.xa.Xid.
This is part of the Java Transaction API in J2EE:
http://java.sun.com/j2ee/transactions.html. Download and install
J2EE 1.2.1 from http
hi, i've this typical error, i've read some stuff about it but many concern applets,
and my problem comes from a jsp page.
i've the jar of distribution load from TOMCAT in it lib directory.
before that i've the 'unable to load class...' Now that i pt the jar in tomcat/lib nad
modify the script
thanks to all for your help,
this a url problem, i thought that the driver problem deal with jar file and not the
code in jsp... newbie in java and postgresql is hard !
Matthieu
-- Mail d'origine --
Matthieu
Can you send us the code which causes the problem. It is very difficult
to di
Barry,
The PreparedStatement references were being held in a Hashtable cache inside
Enhydra. I was never actually using PreparedStatements directly, which was part
of what made finding the problem difficult.
For those who use Enhydra, there is a parameter called "maxPreparedStatements" in
the D
I am confused. It compiles here. I don't understand this patch either.
Can you send a context diff?
> Here is a quick hack to get it to compile properly
>
> Index: Connection.java
> ===
> RCS file:
> /home/projects/pgsql/cvsroot
Matthieu
Can you send us the code which causes the problem. It is very difficult
to diagnose with this much information
Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Matthieu
Guyonnet-Duluc
Sent: August 3, 2001 5:38 AM
To: [EMAIL PROTECTED]
Subj
If people feel that backwards compatibiliy is important I would suggest
it be done in the following way:
A new connection parameter named 'compatible' be defined whose default
value is 7.2 (i.e new functionality). But you could set compatible=7.1
to revert back to the old functionality. (Thi
GUC is how this type of stuff is controlled on the server, but I don't
know of any examples where it controlls client only functionality. Why
would you want parameters on the server that the server doesn't use?
thanks,
--Barry
Bruce Momjian wrote:
>>If people feel that backwards compatibiliy
All,
Please ignore my previous e-mails as I have found where my problem lies and it
is not in the Postgresql driver. Apparently Enhydra uses a prepared statement
cache and the size of my prepared statements and the number of statements being
allowed into the cache (was at 256. I tuned it back t
Barry,
I got OptimizeIt configured, and it looks like it is jdbc2/PreparedStatement
which is not being garbage collected. All of my PreparedStatement s stay
visible in Optimize it and the number of instances never decreases. What
other information can I provide to help determine if this is a me
Index: Connection.java
===
RCS file:
/home/projects/pgsql/cvsroot/pgsql/src/interfaces/jdbc/org/postgresql/Co
nnection.java,v
retrieving revision 1.21
diff -f -r1.21 Connection.java
c1039 1040
info.put("user", PG_USER);
11 matches
Mail list logo