Re: COPY support survey

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: COPY support survey
Date: 2005-08-19 14:42:24
Message-ID: 18287.1124462544@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Kris Jurka <books(at)ejurka(dot)com> writes:
> So the question is what should we do?

> 1) Just get the raw stream interface into the official release and let the
> end user deal with reading and writing the stream. That's all I'll use
> and I don't care about anything else.

> 2) Don't give up, get the friendly SQLInput/SQLOutput interface in because
> this is what I really want.

> 3) Put in the raw stream interface, but keep working to also add the
> friendly one. I'll understand if the interface changes and I have to
> modify my code a bit.

Would it not be possible to do (1) now and leave the door open to add
(2) later without breaking existing uses of (1)? That is, I don't see
why (3) has to carry a risk of non-backwards-compatibility. Surely you
can design non-overlapping APIs for (1) and (2).

(Obviously, my vote is for (3).)

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kevin Grittner 2005-08-19 14:54:44 Re: java.sql.SQLException: ERROR: canceling query due
Previous Message pgsql 2005-08-19 13:49:58 non-polling LISTEN