Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: ms-sql -> pg 8.x


  • 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: Wed, 30 Sep 2009 11:27:38 -0400
  • Message-id: <15511.1254324458@sss.pgh.pa.us> <text/plain>

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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group