Thread: RE: [INTERFACES] JDBC and waiting for commit on a locked table in 6.4.2

I'm not sure about the time out. I'll check the specs.

Talking about 6.5 final, when is the expected date (assuming no show
stopping bugs)? The last date I had heared was May 1st.

I'm way behind on a few fixes in JDBC (work is taking up my time :-( ),
and it would be easier to know of a date to target with.

Peter

--
Peter T Mount, IT Section
petermount@it.maidstone.gov.uk
Anything I write here are my own views, and cannot be taken as the
official words of Maidstone Borough Council

-----Original Message-----
From: Constantin Teodorescu [mailto:teo@flex.ro]
Sent: Tuesday, April 27, 1999 10:13 AM
To: PostgreSQL Interfaces
Subject: [INTERFACES] JDBC and waiting for commit on a locked table in
6.4.2


Hello,

I'm using JDBC PostgreSQL with 6.4.2 database.

I'm using the new code style (conn.setAutoCommit(false)).

When the transaction is waiting for another transaction to terminate, is
there a way to set a timeout period , let's say a maximum of 30 seconds
?
If the lock still persist after 30 seconds the statement.upDate() to
fail and to throw a SQLException?

Of course, without the classical watchdog thread object.

Thanks in advance,

(BTW : I tried the same thing on 6.5 beta 1 and my both transactions
have committed without problem. Nice work that MVCC. I'm watching daily
the development waiting for the big day of 6.5 final)

Best regards,
-- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

Peter Mount wrote:
> 
> I'm not sure about the time out. I'll check the specs.
> 
> Talking about 6.5 final, when is the expected date (assuming no show
> stopping bugs)? The last date I had heared was May 1st.
> 
> I'm way behind on a few fixes in JDBC (work is taking up my time :-( ),
> and it would be easier to know of a date to target with.

Imho, Jun 1st is good date.

?

Vadim