Ok, understood... that could not be so easy anyway :) I supposed that it should be something, that lays in the JDBC specs...
Regards, -- Valentine On Apr 24, 12:28 pm, [EMAIL PROTECTED] (Kris Jurka) wrote: > On Wed, 23 Apr 2008, valgog wrote: > > Is it possible to implement the setStatementTimeout() as somethig > > like: > > > s = c.prepareStatement("SELECT set_config('statement_timeout', > > <neededTimeoutInMilliseconds>, false);" ); > > s.executeQuery(); > > c.commit(); > > Not really. This sets a global timeout for all queries while the JDBC API > specifies that it is per-Statement. Also this only protects against long > running queries. Recently there was some discussion on the JDBC list > about soft vs hard timeouts and it seemed the conclusion was that people > wanted setQueryTimeout to protect against things like the network > connection dropping that statement_timeout can't do. > > In many cases statement_timeout is an adequate substitute for > setQueryTimeout, but not in the general case that the JDBC driver must > implement. > > Kris Jurka > > -- > Sent via pgsql-bugs mailing list ([EMAIL PROTECTED]) > To make changes to your > subscription:http://www.postgresql.org/mailpref/pgsql-bugs -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs