Thread: WIN1252 vs UTF8 database encoding

WIN1252 vs UTF8 database encoding

From
JORGE MALDONADO
Date:
Hi,

I am currently working with a PostgreSQL database created with WIN1252 encoding because the data will be in Spanish language. So, both Collation and Character type are set to Spanish_Mexico.1252

After reading a bit more about encoding, it seems to me that I can use UTF8 encoding so characters for all languages are available and keep Collation and Character type as Spanish_Mexico.1252. I guess that using UTF8 as the encoding method will keep databases more general. I think that using WIN1252 for encoding is restrictive.

Does it make sense?

Regards,
Jorge Maldonado

Re: WIN1252 vs UTF8 database encoding

From
Adrian Klaver
Date:
On 5/4/22 14:51, JORGE MALDONADO wrote:
> Hi,
> 
> I am currently working with a PostgreSQL database created with *WIN1252 
> *encoding because the data will be in Spanish language. So, both 
> *Collation* and *Character type* are set to *Spanish_Mexico.1252*
> 
> After reading a bit more about encoding, it seems to me that I can use 
> *UTF8* encoding so characters for all languages are available and keep 
> *Collation* and *Character type* as *Spanish_Mexico.1252*. I guess that 
> using *UTF8* as the encoding method will keep databases more general. I 
> think that using *WIN1252* for encoding is restrictive.
> 
> Does it make sense?

Yes:

https://www.postgresql.org/docs/current/multibyte.html

"On Windows, however, UTF-8 encoding can be used with any locale."

> 
> Regards,
> Jorge Maldonado


-- 
Adrian Klaver
adrian.klaver@aklaver.com