From: | "Tomi NA" <hefest(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: picking the correct locale when doing initdb |
Date: | 2006-03-16 21:56:33 |
Message-ID: | d487eb8e0603161356pf1aa202rfb205c71b1e2292f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/16/06, Harald Armin Massa <haraldarminmassa(at)gmail(dot)com> wrote:
>
> on bugs Magnus wrote:
>
> > It's a matter of picking the correct locale when you initdb your
> database.
>
> and he is PERFECTLY right. Getting the locale wrong while doing intidb can
> really screw up ones day.
>
> But: because of initdb being at the very beginning, it is a really tough
> decision based on not a lot of information. I know, same problem appears in
> "bigger" databases too.
>
> On the same time my impression is that since PostgreSQL is totally easy to
> install on win32 (ok, still need to understand what are user rights, and
> have ntfs), lots of "first timers" are upgrading from My to Postgre.
>
> What can we do to make their first steps with "encodings" and "locale"
> easier?
>
Here's an idea: let's make the locale a table-level setting, settable at
table creation time so that it's concievable to use postgresql to build,
say, a turist information site supporting english, german, spanish and
italian at the same time.
Tomislav
From | Date | Subject | |
---|---|---|---|
Next Message | CSN | 2006-03-16 21:57:32 | pg_dumpall: permission denied for relation pg_shadow |
Previous Message | Nikolay Samokhvalov | 2006-03-16 21:51:34 | Re: PostgreSQL Knowledge Base |