Re: Collation and Character Type

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: JORGE MALDONADO <jorgemal1960(at)gmail(dot)com>
Cc: pgsql-novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Collation and Character Type
Date: 2020-09-14 22:23:53
Message-ID: CAKFQuwapGa9P4pCnSFuaV0nAkwsSsz+=ZO79T9=5QScyHLPaUg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Mon, Sep 14, 2020 at 3:09 PM JORGE MALDONADO <jorgemal1960(at)gmail(dot)com>
wrote:

> Before clicking on the "Save" button to actually create it, I go to the
> "SQL" tab and I see something like this:
>
> CREATE DATABASE riopoderoso
> WITH
> OWNER = postgres
> TEMPLATE = template0
> ENCODING = 'WIN1252'
> LC_COLLATE = 'Spanish_Mexico.1252'
> LC_CTYPE = 'Spanish_Mexico.1252'
> TABLESPACE = riopoderoso
> CONNECTION LIMIT = -1;
>
> If I want a different value for "LC_COLLATE" and "LC_CYPE", can I just
> copy this code, change such values and run it as a query in the "SQL
> Shell"? Is this a correct procedure?
>

Yes, intercepting the auto-generated SQL command and modifying it is valid
- just remember you need to be connected to a database in order to execute
SQL so if you are not already in that position you will need to do that as
well.

I wonder if I need to do some additional configuration so other character
> sets appear in the "Collation" and "Character type" shown below.
>

You would need to inquire about how that field is populated from the
providers of pgAdmin. If you type in a different value the server will
inform you whether it understands what you mean.

David J.

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Killian Driscoll 2020-09-15 15:00:07 Open version 9.3 .out file with version 12
Previous Message JORGE MALDONADO 2020-09-14 22:08:45 Collation and Character Type