Replied on pgsql-jdbc; please follow the discussion there.
--
Craig Ringer
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
On 12/14/2011 11:30 PM, Sylvain Mougenot wrote:
Thank you Craig Ringer for the detailed list of post (I found some by
myself).
Specially, I'm glad to see it is #1 "TODO" on the compliance matters.
http://jdbc.postgresql.org/todo.html#Compliance
As a reminder, I found post (on the net, not only
Thank you Craig Ringer for the detailed list of post (I found some by
myself).
Specially, I'm glad to see it is #1 "TODO" on the compliance matters.
http://jdbc.postgresql.org/todo.html#Compliance
As a reminder, I found post (on the net, not only on this forum) about this
issue more than 3 years o
On 14/12/2011 9:29 PM, Sylvain Mougenot wrote:
Even if the behaviour is not implemented, I guess it could be "mocked"
if the call to Statement.setQueryTimeout(int seconds) generated the
select statement "SELECT statement_timeout(SEC)".
I know this is not ideal but could solve the problem tempor
On 14/12/2011 9:29 PM, Sylvain Mougenot wrote:
Even if the behaviour is not implemented, I guess it could be "mocked"
if the call to Statement.setQueryTimeout(int seconds) generated the
select statement "SELECT statement_timeout(SEC)".
I know this is not ideal but could solve the problem tempor
Query timeout is not supported in JDBC (driver version 9.1-901.jdbc4)
Statement.setQueryTimeout(int seconds) throws an exception when seconds > 0.
(in drivers prior to 8.3 there was no error but it was ignored)
Using Java + transaction management, we are missing this feature badly.
I found people
