From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Mount <petermount@it.maidstone.gov.uk>
Cc: Lamar Owen <lamar.owen@wgcr.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Cc: Peter Mount (Home) <peter@retep.org.uk>
Subject: Re: [HACKERS] Request for 7.0 JDBC status
Date: Tue, 02 May 2000 12:02:04 -0400
Message-ID: <4100.957283324@sss.pgh.pa.us> (raw)
In-Reply-To: <390EB8E2.6EE3D2DA@alumni.caltech.edu>
References: <200005021102.HAA08318@candle.pha.pa.us>
<390EB8E2.6EE3D2DA@alumni.caltech.edu>
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> Not to bug you Peter, but 7.0 may not wait three days before release.
> I would vote that this is important enough that it should wait, but no
> one has raised the issue until now so we haven't discussed it.
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".
Relevant question: how well does the JDBC code that's in CVS now
work with 7.0? If the answer is "hardly at all" then a new driver
is probably better even if it has lurking bugs. If the answer is
"pretty well" then again I'd be inclined to ship what we've got.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu, pgman@candle.pha.pa.us, petermount@it.maidstone.gov.uk, lamar.owen@wgcr.org, pgsql-hackers@postgresql.org, peter@retep.org.uk
Subject: Re: [HACKERS] Request for 7.0 JDBC status
In-Reply-To: <4100.957283324@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox