Skip site navigation (1) Skip section navigation (2)

COPY support survey

From: Kris Jurka <books(at)ejurka(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: COPY support survey
Date: 2005-08-19 07:03:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
On and off there's been discussions of getting COPY support into the JDBC 
driver and I produced a patch to provide a stream based interface over a 
year and a half ago [1].  At the time we did not commit that because we 
had grand plans to provide a friendly interface to users so they did not 
have to know the internals of how COPY actually represents data.  This 
mostly happened off-list between Oliver and I, but the key suggestion is 
available here [2].  This allows you to use SQLOutput [3] calls like 
writeTimestamp or writeArray to directly send Java objects to the database 
without having to know the Postgresql specific text representation of 
them.  This turned out to be harder and more involved than it looked and I 
just let the patch languish, always intending to return to it, but as time 
has passed I've actually had less time to dedicate to the driver instead 
of more.

I know a number of people are already/still using the original patch I 
provided, but at the same time they have also (indirectly) indicated that 
some additional support is needed [4].

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.

Kris Jurka



pgsql-jdbc by date

Next:From: Dave CramerDate: 2005-08-19 12:07:17
Subject: Re: COPY support survey
Previous:From: Kris JurkaDate: 2005-08-19 05:34:38
Subject: Re: Updated high-unicode patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group