From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Supporting SJIS as a database encoding |
Date: | 2016-09-05 07:38:54 |
Message-ID: | 20160905.163854.612818171756520492.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> But what I'm wondering is why PostgreSQL doesn't support SJIS. Was there any technical difficulty? Is there anything you are worried about if adding SJIS?
Yes, there's a technical difficulty with backend code. In many places
it is assumed that any string is "ASCII compatible", which means no
ASCII character is used as a part of multi byte string. Here is such a
random example from src/backend/util/adt/varlena.c:
/* Else, it's the traditional escaped style */
for (bc = 0, tp = inputText; *tp != '\0'; bc++)
{
if (tp[0] != '\\')
tp++;
Sometimes SJIS uses '\' as the second byte of it.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2016-09-05 08:00:06 | Re: Supporting SJIS as a database encoding |
Previous Message | Tsunakawa, Takayuki | 2016-09-05 07:23:21 | Supporting SJIS as a database encoding |