From: | Sam Varshavchik <mrsam(at)courier-mta(dot)com> |
---|---|
To: | |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: COPY support in pgsql-jdbc driver |
Date: | 2002-06-20 16:35:57 |
Message-ID: | courier.3D12046D.00005524@ny.email-scan.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Barry Lind writes:
> Sam Varshavchik wrote:
>
>> What's being dumped and reloaded here is a byte-stream
>> (InputStream/OutputStream), not a character-stream (Reader/Writer).
>> Presumably, the only thing that's ever going to be reloaded something
>> that was dumped previously, so no conversions are necessary.
>
> This is not correct. The data coming from the server is a stream of
> characters in the character encoding of the server. This character
> encoding may be different than the client character encoding, and
> therefore character set conversions are necessary. Lets say for example
> the database is running with UTF-8 as it's character set, thus the output
> of the copy will be UTF-8 encoded. If the client is running Latin1 then
> there will be a missmatch and all 8bit characters will be interpreted
> incorrectly by the client. Character set conversion is necessary in this
> case.
That only matters if you actually want to do something with the dumped data.
If all you want is to be able to reload it later, why bother converting
charset A to B, only to have it converted from B to A later?
--
Sam
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-06-20 17:11:49 | Re: COPY support in pgsql-jdbc driver |
Previous Message | Barry Lind | 2002-06-20 15:50:31 | Re: COPY support in pgsql-jdbc driver |