Tom Lane wrote: > Jessica Perry Hekman <[EMAIL PROTECTED]> writes: > > [snip] > > My proposal, then, is that the Java driver should submit the > > transaction request; wait for the timeout; if it goes off, submit a > > cancel request; and then throw a SQLException. We would not handle > > this in the backend at all. > > > Bruce agreed that this was a good point to ask what the rest of the > > hackers list thought. Any input? > > I guess the $64 question is whether any frontends other than JDBC want > this behavior. If it's JDBC-only then I'd certainly vote for making > JDBC handle it ... but as soon as we see several different frontends > implementing similar behavior, I'd say it makes sense to implement it > once in the backend. > > So, what's the market?
There is clearly interest from all interfaces. This item has been requested quite often, usually related to client apps or web apps. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
