MIME-Version: 1.0
References: <CA+FnnTyJDvLijfizguNahiRO1LMHR4t9=_9-aO8P18cDZ6RRGA@mail.gmail.com>
 <CANzqJaB=zwoYT_rBwUX8q4VyqQBGWyjvAiW=UAJZ0+eh7HU0Zg@mail.gmail.com>
 <CA+FnnTwpjzm+QNTtyx=J8LGmbS90ceVWaysfzbo-OxNi5Fq2kA@mail.gmail.com> <CANzqJaABDxgMYHOWVKFgZC-B1-JznyyghCPHVbwUR9datT-MWg@mail.gmail.com>
In-Reply-To: <CANzqJaABDxgMYHOWVKFgZC-B1-JznyyghCPHVbwUR9datT-MWg@mail.gmail.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Sun, 3 May 2026 16:51:32 -0500
Message-ID: <CA+FnnTz0bXuTUR5CqXNM5xR3UM9MbTOkYdUP5rUNGSQxZaznXg@mail.gmail.com>
Subject: Re: Choosing default collation/ctype
To: Ron Johnson <ronljohnsonjr@gmail.com>, 
	"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTz0bXuTUR5CqXNM5xR3UM9MbTOkYdUP5rUNGSQxZaznXg%40mail.gmail.com>
Precedence: bulk

Hi, Ron.

On Sun, May 3, 2026 at 4:05=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.com=
> wrote:
>
> On Sun, May 3, 2026 at 4:52=E2=80=AFPM Igor Korot <ikorot01@gmail.com> wr=
ote:
>>
>> Hi,
>>
>> On Sun, May 3, 2026 at 3:09=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.=
com> wrote:
>> >
>> > On Sun, May 3, 2026 at 3:52=E2=80=AFPM Igor Korot <ikorot01@gmail.com>=
 wrote:
>> >>
>> >> Hi, ALL,
>> >> In the CREATE DATABASE statement I can use encoding/collation/ctype.
>> >>
>> >> I can retrieve the encoding list with:
>> >>
>> >> [code]
>> >> SELECT pg_encoding_to_char( conforencoding ) AS name FROM pg_conversi=
on
>> >> [/code]
>> >>
>> >> And then I can get a list of collations/ctypes with:
>> >>
>> >> [code]
>> >> SELECT collname, collencoding, collprovider collctype FROM pg_collati=
on
>> >> [/code]
>> >>
>> >> And then add a logic in my UI to switch collations/ctypes based on en=
coding.
>> >>
>> >> However, what I wonder is:
>> >>
>> >> Is there a way to select a default collation/ctype for a specific enc=
oding?
>> >>
>> >> Or maybe I'm overthinking it and I should let the user choose and if
>> >> nothing - just keep those 2 as "Default" and let the server pick it
>> >> up. However it will be weird, especially from me as a user POV.
>> >
>> >
>> > You know your data, not us.  The first question I'd try to is "how muc=
h client text data is not compatible with bog-standard UTF8?"
>>
>> I don't.
>> Just trying to create a generic tool to use for people everywhere...
>
>
> Then choose UTF8.

Let me give you a quick run of what I'm trying to do:

In my code I have 3 combo boxes: encoding, collation and ctype.

Initially they all have a value of "Default".

Lets say a user selected "KOI8-R" as an emcoding.

What I will do is populate collation and ctype combo boxes with
values available for such encodings.
But I want to go a little further and change the values in those
to be the default collation/ctype for the "KOI8-R" encoding.

Now are you saying I should choose the one that have "UTF8"
in it?

Thank you.

>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!