From: | "Michael Nacos" <m(dot)nacos(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: COPY support in JDBC driver? |
Date: | 2008-09-24 14:06:40 |
Message-ID: | 407fa4640809240706s797ce2d0ic36b01d2e9558ab5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi Mark,
if you want COPY support from the JDBC driver just for performance reasons,
you should probably also consider using the driver's batch mode. Please have
a look at the following links:
http://archives.postgresql.org/pgsql-jdbc/2007-04/msg00076.php
http://freeyourtech.wordpress.com/2008/07/15/using-postgresql-jdbc-for-bulk-updates-batch-size-vs-performance/
Encoding is a serious consideration. While testing pgBee, I ran into
problems inserting codepage 1252 files into a SQL_ASCII database, because of
character mismatches. In your Java application, you may specify a particular
charset for reading the input files. I haven't used the patch, but if
support for the COPY operation is to be included in the driver, please make
sure the driver handles such things with care.
It might also be that the driver shouldn't have to deal with things like
that. It's a driver for connecting to a DBMS, not a backup-restore solution.
But I cannot speak on behalf of anyone or anything, I'm pretty much an
occasional pgsql-jdbc reader.
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Migowski | 2008-09-24 14:41:53 | Re: COPY support in JDBC driver? |
Previous Message | Matt Magoffin | 2008-09-24 06:34:41 | Re: very large result sets and ResultSet.relative() to jump to a desired offset |