From 1eef90d0a21167c4043c7d8cacaa0e937c9eb8e8 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Mon, 6 Apr 2009 08:42:53 +0000 Subject: Rename the new CREATE DATABASE options to set collation and ctype into LC_COLLATE and LC_CTYPE, per discussion on pgsql-hackers. --- doc/src/sgml/charset.sgml | 4 ++-- doc/src/sgml/keywords.sgml | 6 +++--- doc/src/sgml/ref/create_database.sgml | 12 ++++++------ 3 files changed, 11 insertions(+), 11 deletions(-) (limited to 'doc/src/sgml') diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 72a77a873c9..715824f21df 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -749,7 +749,7 @@ createdb -E EUC_KR -T template0 --lc-collate=ko_KR.euckr --lc-ctype=ko_KR.euckr Another way to accomplish this is to use this SQL command: <programlisting> -CREATE DATABASE korean WITH ENCODING 'EUC_KR' COLLATE='ko_KR.euckr' CTYPE='ko_KR.euckr' TEMPLATE=template0; +CREATE DATABASE korean WITH ENCODING 'EUC_KR' LC_COLLATE='ko_KR.euckr' LC_CTYPE='ko_KR.euckr' TEMPLATE=template0; </programlisting> The encoding for a database is stored in the system catalog diff --git a/doc/src/sgml/keywords.sgml b/doc/src/sgml/keywords.sgml index 5ea6da68a68..e7641dc4683 100644 --- a/doc/src/sgml/keywords.sgml +++ b/doc/src/sgml/keywords.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/keywords.sgml,v 2.23 2009/02/24 10:06:31 petere Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/keywords.sgml,v 2.24 2009/04/06 08:42:52 heikki Exp $ --> <appendix id="sql-keywords-appendix"> <title><acronym>SQL</acronym> Key Words @@ -800,7 +800,7 @@ non-reserved - COLLATE + LC_COLLATE reserved reserved reserved @@ -1168,7 +1168,7 @@ - CTYPE + LC_CTYPE non-reserved diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 05b3177201a..5866ca7ef5c 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -1,5 +1,5 @@ @@ -25,8 +25,8 @@ CREATE DATABASE name [ [ WITH ] [ OWNER [=] dbowner ] [ TEMPLATE [=] template ] [ ENCODING [=] encoding ] - [ COLLATE [=] collate ] - [ CTYPE [=] ctype ] + [ LC_COLLATE [=] lc_collate ] + [ LC_CTYPE [=] lc_ctype ] [ TABLESPACE [=] tablespace ] [ CONNECTION LIMIT [=] connlimit ] ] @@ -207,7 +207,7 @@ CREATE DATABASE name The character set encoding specified for the new database must be - compatible with the chosen COLLATE and CTYPE settings. + compatible with the chosen LC_COLLATE and LC_CTYPE settings. If LC_CTYPE is C (or equivalently POSIX), then all encodings are allowed, but for other locale settings there is only one encoding that will work properly. @@ -219,9 +219,9 @@ CREATE DATABASE name - The COLLATE and CTYPE settings must match + The LC_COLLATE and LC_CTYPE settings must match those of the template database, except when template0 is used as - template. This is because COLLATE and CTYPE + template. This is because LC_COLLATE and LC_CTYPE affects the ordering in indexes, so that any indexes copied from the template database would be invalid in the new database with different settings. template0, however, is known to not -- cgit v1.2.3