| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | Sydney Puente <sydneypuente(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ms-sql -> pg 8.x |
| Date: | 2009-09-30 15:27:38 |
| Message-ID: | 15511.1254324458@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> Sydney Puente wrote:
>> The first isssue that occurs to me is that CP1252 is used throughout
>> the data and there is a lot of european special characters, e acute
>> for example. But the column names etc are regular chars [a-zA-Z].
> CP1252 aka Windows-1252 is actually pretty close to ISO-8859-1 aka
> LATIN1. The differences are mostly that CP1252 uses the 80-9F section
> for additional characters, this is unused in LATIN1.
> Personally, I'd probably make the Postgres database UTF-8, then use
> Windows-1252 as the client_encoding during the import process.
FWIW, we do support win1252 as a database encoding. I tend to agree
that switching to something better-standardized would be a good idea
though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivano Luberti | 2009-09-30 15:34:43 | error message and documentation |
| Previous Message | John R Pierce | 2009-09-30 15:21:14 | Re: automated row deletion |