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

Re: [JDBC] Support for JDBC setQueryTimeout, et al.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, david(at)fetter(dot)org, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org, rsmogura(at)softperience(dot)eu
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Date: 2010-10-21 17:57:59
Message-ID: 27301.1287683879@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> Tom Lane  wrote:
>>> I'm all for doing this client-side.

> Uh, why would we do this client-side rather than server-side?  If we do
> it server-side, all interfaces get it.

1. The API that's being implemented is JDBC-specific.

2. Even if you want to argue that it would be generally useful to have
such a feature, it would certainly require additional client-side
programming to make each client interface make use of it.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-10-21 17:59:04
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous:From: Kevin GrittnerDate: 2010-10-21 17:50:53
Subject: Re: Domains versus arrays versus typmods

pgsql-jdbc by date

Next:From: Bruce MomjianDate: 2010-10-21 17:59:04
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous:From: dmpDate: 2010-10-21 17:57:01
Subject: Re: Bug in DatabaseMetaData.getColumns() with columns based on domains

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