On 28 Sep 2006, at 21:01 , Julian 'Julik' Tarkhanov wrote:
On 28-sep-2006, at 4:00, Michael Glaesemann wrote:
In PostgreSQL, encoding is a database-level setting, not a table attribute. I
AFAIK it's customizable all the way, from the cluster to the database to the tables and columns.

You can set the encoding on multiple levels, but you can only set the locale, which defines the collation when you create the 'database cluster'. You can get a list of available locales on your system with locale -a

And the locale of the postmaster user plays it's part too.

Only if you so not set the local when you create the 'database cluster'.

The easiest way that we could find to do UTF-8 with PostgreSQL is to first create the 'database cluster' with:

  $ initdb --locale=en_GB.UTF-8 -D data_dir

...and then create the databases with something like:

  $ createdb --encoding=UTF8 db_name

And yes, you've read it right, you can only get _one collation type_ for your cluster...

Kind regards,
Thijs

--
Fingertips - http://www.fngtps.com

Phone: +31 (0)6 24204845
Skype: tvandervossen

MSN Messenger: [EMAIL PROTECTED]
iChat/AOL:  [EMAIL PROTECTED]
Jabber IM: [EMAIL PROTECTED]



Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to