On Jul 23, 2010, at 7:11 AM, Tom Lane wrote:
> I can't help thinking that the JDBC driver must be being overly cute
> if this breaks it ...
I was wondering the same thing when I first saw Kris' message. However, iff I understand what JDBC is trying to achieve, I don't think I would call it "overly".
Is this a problem because JDBC is trying to detect failures as early as possible during a COPY IN?
Or, is it just JDBC's normal MO to always be reading?
Well, I've wanted to do the former (early error detection) with py-postgresql's COPY support, and I imagine getting a read event marking completion prior to emitting done/fail could be a snag.
In response to
pgsql-hackers by date
|Next:||From: Joseph Adams||Date: 2010-07-25 02:34:53|
|Subject: patch: utf8_to_unicode (trivial)|
|Previous:||From: Andres Freund||Date: 2010-07-25 00:22:36|
|Subject: Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)|
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2010-07-25 15:01:48|
|Subject: Re: [HACKERS] Trouble with COPY IN |
|Previous:||From: Radosław Smogura||Date: 2010-07-24 15:21:00|
|Subject: Re: Binary protocol support for JDBC|