| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Barry Lind <blind(at)xythos(dot)com> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, Markus Schaber <schabios(at)logi-track(dot)com>, pgsql-jdbc(at)postgresql(dot)org, mbch67(at)yahoo(dot)com |
| Subject: | Re: 8.0.0beta4: "copy" and "client_encoding" |
| Date: | 2004-11-08 22:07:12 |
| Message-ID: | 418FEE10.5020601@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Barry Lind wrote:
> If you choose to go the URL parameter route, I would suggest you use the
> existing 'compatible' parameter. This is exactly the type of thing that
> parameter was designed to be used for. By default the driver does the
> new check. But with a value of 'compatible=7.4' (or less, i.e. < 8.0)
> the driver would revert back to the old behavior of not doing this
> check.
What's the upgrade path for a "legacy" application that uses COPY, so
that it is a "current" application and no longer needs the compatible=
parameter?
I don't see such a path without an additional COPY API or backend
changes. So I'd prefer not to put this into the "compatible behaviour"
bucket.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J. Michael Crawford | 2004-11-09 00:03:47 | Re: [JDBC] Using Postgres with Latin1 (ISO8859-1) |
| Previous Message | Oliver Jowett | 2004-11-08 21:55:55 | Re: [JDBC] Using Postgres with Latin1 (ISO8859-1) |