From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: SQL_ASCII and UNICODE server_encoding
Date: Mon, 16 Aug 2004 11:04:33 -0400
Message-ID: <13567.1092668673@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0408161640340.29016-100000@matrix.gatewaynet.com>
References: <Pine.LNX.4.44.0408161640340.29016-100000@matrix.gatewaynet.com>
Achilleus Mantzios <achill@matrix.gatewaynet.com> writes:
> So if SQL_ASCII should be fine for UTF-8 storage.
> (here i must have missed something, tho..), whats
> the purpose of server_encoding=UNICODE?
If you use SQL_ASCII, the server will *store* Unicode just fine, but
it won't *know* it is Unicode. So if you just want raw data storage
it doesn't matter. If you would like to sort the data, upper-case
or lower-case it, or have automatic conversions to different client
encodings, you had better tell the server the truth about what it
is storing.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, achill@matrix.gatewaynet.com
Subject: Re: SQL_ASCII and UNICODE server_encoding
In-Reply-To: <13567.1092668673@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox