From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | JORGE MALDONADO <jorgemal1960(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: WIN1252 vs UTF8 database encoding |
Date: | 2022-05-04 22:27:03 |
Message-ID: | ac7ff009-0eeb-f110-3070-ecf4efce7a44@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Farber | 2022-05-05 10:44:23 | Re: Displaying chat by punished users only to themselves (db fiddle attached) |
Previous Message | JORGE MALDONADO | 2022-05-04 21:51:04 | WIN1252 vs UTF8 database encoding |