Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Java threads and the JDBC driver

From: Peter T Mount <peter(at)retep(dot)org(dot)uk>
To: Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] Java threads and the JDBC driver
Date: 1998-09-14 18:15:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
On Mon, 14 Sep 1998, Herouth Maoz wrote:

> As I understand it, the JDBC driver is not thread safe.
> I am trying to figure out how much synchronization I need.
> Is it safe to use separate ResultSets that originate from the same
> Connection object concurrently? That is, lock the connection object, create
> and perform the query into a new ResultSet, unlock the connection, and
> proceed to use the ResultSet? If I do that, other threads may be issuing
> queries while I'm still looping on the ResultSet.

As long as the query is done with a different Statement object, then in
theory yes. The api states that any existing ResultSet is closed when
executeQuery() or executeUpdate() is run, but you can have as many
Statement's as you want.

> It's supposed to be OK. But is it?

Now with our driver, all queries are actually done with the
Connection.ExecSQL() method.

Now that method is already syncronized, so it may work. I'll make up a
test, and see what happens. 

       Peter T Mount peter(at)retep(dot)org(dot)uk
      Main Homepage:
PostgreSQL JDBC Faq:
 Java PDF Generator:

In response to

pgsql-interfaces by date

Next:From: Mikael HammarinDate: 1998-09-15 07:48:39
Subject: userid bug?
Previous:From: Herouth MaozDate: 1998-09-14 13:05:16
Subject: Java threads and the JDBC driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group