X-Original-To: pgsql-jdbc-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 412EFD1B1DA for ; Mon, 7 Jun 2004 07:22:31 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 04501-04 for ; Mon, 7 Jun 2004 10:22:28 +0000 (GMT) Received: from mail63.csoft.net (unknown [63.111.22.74]) by svr1.postgresql.org (Postfix) with SMTP id 87674D1B26D for ; Mon, 7 Jun 2004 07:22:24 -0300 (ADT) Received: (qmail 31580 invoked by uid 1112); 7 Jun 2004 09:26:38 -0000 Date: Mon, 7 Jun 2004 04:26:38 -0500 (EST) From: Kris Jurka X-X-Sender: books@leary.csoft.net To: Steve Wampler Cc: Postgres-JDBC , Postgres-performance Subject: Re: Using a COPY...FROM through JDBC? In-Reply-To: <1086466349.29063.76.camel@weaver.tuc.noao.edu> Message-ID: References: <1086466349.29063.76.camel@weaver.tuc.noao.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/33 X-Sequence-Number: 10235 On Sat, 5 Jun 2004, Steve Wampler wrote: > > [I want to use copy from JDBC] > I made a patch to the driver to support COPY as a PG extension. The patch required properly encoded and formatted copy data available from an InputStream. Following some feedback from others I began adding the ability to handle different encodings and the ability to read and write objects without requiring any knowledge of the copy data format. I got hung up on the object read/write part because of some issues with how type conversions are done in the driver. At the moment there is a big push being made by Oliver Jowett to get true V3 protocol support implemented which is currently my highest priority. Getting copy support into the JDBC driver is something I'd like to see for 7.5, but I couldn't say if that will happen or how complete it may be. Depending on your needs perhaps the initial patch is sufficient. http://archives.postgresql.org/pgsql-jdbc/2003-12/msg00186.php Kris Jurka