| From: | "arnuld uttre" <arnuld(dot)mizong(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DB and Unicode problem (was: user and DB confusion) |
| Date: | 2008-10-13 12:03:24 |
| Message-ID: | 3a97b5b90810130503h3547273fjaf5a14b216fcfa60@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Mon, Oct 13, 2008 at 5:11 PM, Tino Wildenhain <tino(at)wildenhain(dot)de> wrote:
> Well exactly that. What information is missing?
>
> There is a parameter on createdb command line
> (As well as CREATEDB command in SQL) which
> needs to be set to unicode.
yes my friend :) -E utf8
thanks
> Hint: to get collation right, you might want to
> initdb first (with empty $PGDATA) with correct
> locale settings (including charset UTF-8 which will
> then be the default encoding for all subsequent
> created databases.
default is ISO-8859. I can't make it to UTF8 because then my VLC stops
working :\ . Quite very unusual problem.
--
http://uttre.wordpress.com/2008/05/14/the-lost-love-of-mine/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Dzhuvinov | 2008-10-13 12:09:26 | Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
| Previous Message | Ivan Sergio Borgonovo | 2008-10-13 11:41:31 | multi recordset and data type check was: Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |