Re: 8.0.0beta4: "copy" and "client_encoding"
От | Markus Schaber |
---|---|
Тема | Re: 8.0.0beta4: "copy" and "client_encoding" |
Дата | |
Msg-id | 20041109183626.32f44aba@kingfisher.intern.logi-track.com обсуждение исходный текст |
Ответ на | Re: 8.0.0beta4: "copy" and "client_encoding" (Oliver Jowett <oliver@opencloud.com>) |
Список | pgsql-jdbc |
Hi, Oliver, On Tue, 09 Nov 2004 11:07:12 +1300 Oliver Jowett <oliver@opencloud.com> 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? The upgrade path is to use properly recoded files. > 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. Maybe the sanest way would be to have an extra parameter, but setting compatible=7.4 also disables the check. But this may be to confusing. Markus -- markus schaber | dipl. informatiker logi-track ag | rennweg 14-16 | ch 8001 zürich phone +41-43-888 62 52 | fax +41-43-888 62 53 mailto:schabios@logi-track.com | www.logi-track.com
В списке pgsql-jdbc по дате отправления: