From: | Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: SQL_ASCII and UNICODE server_encoding |
Date: | 2004-08-16 14:42:02 |
Message-ID: | Pine.LNX.4.44.0408161741160.29055-100000@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
O kyrios Tom Lane egrapse stis Aug 16, 2004 :
> 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.
Thanx, i guess i didnt realize the value of conversion,sorting,etc...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
-Achilleus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-16 15:04:33 | Re: SQL_ASCII and UNICODE server_encoding |
Previous Message | Tom Lane | 2004-08-16 14:28:42 | Re: Inheriting text[] field |