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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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:
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
From | Date | Subject | |
---|---|---|---|
Next Message | Lew | 2010-11-12 13:41:20 | Re: PSQLException: The column name <col> was not found in this ResultSet. |
Previous Message | Maciek Sakrejda | 2010-11-12 06:18:32 | Re: PSQLException: The column name <col> was not found in this ResultSet. |