Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2JNsPN16385; Mon, 19 Mar 2001 18:54:25 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id SAA11684; Mon, 19 Mar 2001 18:54:05 -0500 (EST) From: Bruce Momjian Message-Id: <200103192354.SAA11684@candle.pha.pa.us> Subject: Re: [JDBC] Re: PostgreSQL and PHP persistent connections In-Reply-To: "from Gunnar R|nning at Mar 19, 2001 11:38:39 pm" To: "Gunnar R|nning" Date: Mon, 19 Mar 2001 18:54:05 -0500 (EST) CC: Peter Mount , "Thies C. Arntzen" , pgsql-jdbc@postgresql.org, PostgreSQL-interfaces X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/148 X-Sequence-Number: 1309 > Bruce Momjian writes: > > > > > I don't think that belongs in jdbc. It is the connection pooling code > > that should execute those statements before passing over a new > > connection. No reason to have it for all jdbc users. > > Well, I think most connection pools people use are database independent - > when it comes to JDBC this is the case at least. So what platform-indendent method do they use to see that the passed connection doesn't have an open transaction or some other setting? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026