Re: SQL_ASCII and UNICODE server_encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: SQL_ASCII and UNICODE server_encoding
Date: 2004-08-16 15:04:33
Message-ID: 13567.1092668673@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Markus Bertheau 2004-08-16 20:15:49 any chance SQL ASSERTIONS will be implemented?
Previous Message Achilleus Mantzios 2004-08-16 14:42:02 Re: SQL_ASCII and UNICODE server_encoding