| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Michael Adler <adler(at)glimpser(dot)org> |
| Cc: | Dave Cramer <Dave(at)micro-automation(dot)net>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, Barry Lind <blind(at)xythos(dot)com> |
| Subject: | Re: patch for COPY |
| Date: | 2003-02-08 02:47:18 |
| Message-ID: | Pine.LNX.4.33.0302072140210.5842-100000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
One of the failings of the copy protocol is that on error basically the
connection is hosed. Is it possible to reset the connection state on
error for the user?
Also are there plans to support other elements of the COPY syntax? For
example NULL AS, OIDS, and column lists.
Kris Jurka
On Fri, 7 Feb 2003, Michael Adler wrote:
>
> I've attached a tar file that includes a context diff and two additional
> files. This should provide COPY capabilities for the JDBC driver. I can
> write up the Docbook documentation if the patch (or some version of it) is
> to be incorporated.
>
> I will be unable to respond to comments next week, but I can respond this
> weekend and the following weekend and thereafter.
>
> - Mike Adler
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2003-02-08 03:19:36 | Re: debugging prepared statements |
| Previous Message | Jeremiah Jahn | 2003-02-07 22:01:22 | PreparedStatement.executeBatch() error? 7.3 |