Re: PGobject overhaul (was Re: tightening up on use of oid

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: PGobject overhaul (was Re: tightening up on use of oid
Date: 2004-10-30 15:43:50
Message-ID: Pine.BSO.4.56.0410301013050.10973@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Thu, 28 Oct 2004, Oliver Jowett wrote:

> For PGobject it turned into a bit of a general overhaul. Currently I have:

These changes are way too drastic for something as minor as preventing a
user from accidentally mutating a NULL PGobject. These API changes suck
for both developers and users. There's no way to make a PGobject
implementation compile against both 7.4 and 8.0 drivers. Altering the
PGline API means user code can't compile against both 7.4 and 8.0 drivers.

If we were providing exciting new features, then maybe, but for now we've
got to find a way to make this work without huge API changes or we should
abandon the whole idea and go back to your original patch. What
immediately comes to mind is making the PGobject interface an abstract
class with all abstract methods so that a developer can implement a type
that can work with both driver versions.

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Euler Taveira de Oliveira 2004-10-30 22:53:16 Translation update: pt_BR
Previous Message Kris Jurka 2004-10-29 23:20:14 Re: setQueryTimeOut