Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitd596736

Browse files
committed
Doc: fix character_sets view.
The note regarding character encoding form in "The Information Schema"said that LATIN1 character repertoires only use one encoding formLATIN1. This is not correct because LATIN1 has another encoding formISO-2022-JP-2. To fix this, replace LATIN1 with LATIN2, which is notsupported by ISO-2022-JP-2, thus it can be said that LATIN2 only usesone encoding form.Back-patch to supported branches.Author: Tatsuo IshiiReviewed-by: Daniel GustafssonDiscussion:https://postgr.es/m/flat/20240102.153925.1147403616414525145.t-ishii%40sranhm.sra.co.jp
1 parent028b154 commitd596736

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/information_schema.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -697,8 +697,8 @@
697697
<para>
698698
An encoding of some character repertoire. Most older character
699699
repertoires only use one encoding form, and so there are no
700-
separate names for them (e.g., <literal>LATIN1</literal> is an
701-
encoding form applicable to the <literal>LATIN1</literal>
700+
separate names for them (e.g., <literal>LATIN2</literal> is an
701+
encoding form applicable to the <literal>LATIN2</literal>
702702
repertoire). But for example Unicode has the encoding forms
703703
<literal>UTF8</literal>, <literal>UTF16</literal>, etc. (not
704704
all supported by PostgreSQL). Encoding forms are not exposed

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp