Re: Significance of Database Encoding

From: PFC <lists(at)boutiquenumerique(dot)com>
To: "Rajesh Mallah" <mallah_rajesh(at)yahoo(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Significance of Database Encoding
Date: 2005-05-15 17:02:37
Message-ID: op.sqttmnyhth1vuj@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


> +--------------------------------------------------------------------------------------+
> | &#31169;&#12399;&#12460;&#12521;&#12473;
> +--------------------------------------------------------------------------------------+

You say it displays correctly in xterm (ie. you didn't see these in your
xterm).
There are HTML/XML unicode character entities, probably generated by your
mailer from your Unicode cut'n'paste.
Using SQL ASCII to store UTF8 encoded data will work, but postgres won't
know that it's manipulating multibyte characters, so for instance the
length of a string will be its Byte length instead of correctly counting
the characters, collation rules will be funky, etc. And substring() may
well cut in the middle of an UTF8 multibyte char which will then screw
your application side processing...
Apart from that, it'll work ;)

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Rajesh Mallah 2005-05-15 18:38:29 Re: Significance of Database Encoding
Previous Message Rajesh Mallah 2005-05-15 16:16:13 Re: Significance of Database Encoding [ update ]