Re: Supporting SJIS as a database encoding
От | Tatsuo Ishii |
---|---|
Тема | Re: Supporting SJIS as a database encoding |
Дата | |
Msg-id | 20160905.163854.612818171756520492.t-ishii@sraoss.co.jp обсуждение исходный текст |
Ответ на | Supporting SJIS as a database encoding ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
Ответы |
Re: Supporting SJIS as a database encoding
|
Список | pgsql-hackers |
> But what I'm wondering is why PostgreSQL doesn't support SJIS. Was there any technical difficulty? Is there anythingyou 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
В списке pgsql-hackers по дате отправления: