| From: | Michael Adler <adler(at)glimpser(dot)org> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| 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 14:57:23 |
| Message-ID: | Pine.NEB.4.53.0302080924270.3347@reva.sixgirls.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 7 Feb 2003, Kris Jurka wrote:
> 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?
Assuming the rest of the driver can support this behavior, I'm guess that
we should make this optional.
> Also are there plans to support other elements of the COPY syntax? For
> example NULL AS, OIDS, and column lists.
Yes. My current thinking is to provide a method that takes an arbitrary
COPY command. This also gives us backwards compatibility since the command
syntax has changed from 7.2 to 7.3.
Mike Adler
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Katzmann | 2003-02-08 15:42:55 | Re: Timestamp problems |
| Previous Message | Barry Lind | 2003-02-08 03:34:27 | Re: PreparedStatement.executeBatch() error? 7.3 |