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

Re: PSQLException: The column name <col> was not found in this ResultSet.

From: Till Toenges <tt(at)kyon(dot)de>
To: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
Cc: Lew <noone(at)lewscanon(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: PSQLException: The column name <col> was not found in this ResultSet.
Date: 2010-11-12 06:22:58
Message-ID: 4CDCDD42.6080103@kyon.de (view raw or flat)
Thread:
Lists: pgsql-jdbc
On 2010-11-12 07:18, Maciek Sakrejda wrote:
> We're getting off topic--perhaps I didn't express myself clearly.
> Getting back to Samuel's original point, if the ResultSet interface
> contract does not require a given implementation to provide thread
> safety for these operations--and it appears that it does not--then
> maybe pgjdbc should not try to provide it. If a user needs to use a
> ResultSet from multiple threads, it can be synchronized externally.

The pgjdbc driver is supposed to be thread safe:

http://jdbc.postgresql.org/documentation/pgjdbc.html#Using+the+Driver+in+a+Multithreaded+or+a+Servlet+Environment

Whether this is good or bad doesn't matter. Has been this way forever, 
can't change that now.


Till

-- 
Kyon, Till Toenges, tt(at)kyon(dot)de, http://kyon.de
Blumenstr. 39, 47798 Krefeld, +49-2151-3292595

In response to

Responses

pgsql-jdbc by date

Next:From: LewDate: 2010-11-12 13:41:20
Subject: Re: PSQLException: The column name <col> was not found in this ResultSet.
Previous:From: Maciek SakrejdaDate: 2010-11-12 06:18:32
Subject: Re: PSQLException: The column name <col> was not found in this ResultSet.

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