Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA84805; Wed, 3 May 2000 00:20:07 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id EAA09980; Wed, 3 May 2000 04:21:04 GMT Message-ID: <390FA930.6F489F9B@alumni.caltech.edu> Date: Wed, 03 May 2000 04:21:04 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: Bruce Momjian , Peter Mount , Lamar Owen , PostgreSQL-development , PostgreSQL-interfaces , "Peter Mount (Home)" Subject: Re: [HACKERS] Request for 7.0 JDBC status References: <200005021102.HAA08318@candle.pha.pa.us> <390EB8E2.6EE3D2DA@alumni.caltech.edu> <4100.957283324@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/46 > My two cents: I wouldn't object to postponing release a day or so for > it, *but* if what we're getting is an un-beta-tested driver then my > level of enthusiasm drops considerably. I'd rather say "it'll get > fixed in 7.0.1, after a decent testing interval for the new driver". Both versions of JDBC are in the Postgres source code tree. The newer version has more standard conventions for Java namespaces (right term??) and improvements in conformance to later versions of the JDBC spec. Basically the stuff is there already, and we just have a few file updates to get it finalized. I'd be suprised if it is not ready by the weekend, so it shouldn't be much of an issue. - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California