On Jul 28, 2006, at 12:37 , ISHIDA Akio wrote:

> | SJIS $B%5!<%P$NId9f2=J}<0$H$7$F$O%5%]!<%H$7$F$$$^$;$s!#(B

Just to confirm, it does look like there's a discrepancy between what
is in the documentation and the actual behavior of the server. The
documentation indicates that SJIS is a valid server encoding:

http://www.postgresql.org/docs/current/interactive/
multibyte.html#MULTIBYTE-CHARSET-SUPPORTED

I just tried to create a database with SJIS encoding using the
various aliases listed and was unable to do so:

grzm$ createdb shift_jis --encoding SJIS
createdb: database creation failed: ERROR: SJIS is not a valid
encoding name
grzm$ createdb shift_jis --encoding SHIFT_JIS
createdb: database creation failed: ERROR: SHIFT_JIS is not a valid
encoding name
grzm$ createdb shift_jis --encoding Mskanji
createdb: database creation failed: ERROR: Mskanji is not a valid
encoding name
grzm$ createdb shift_jis --encoding WIN932
createdb: database creation failed: ERROR: WIN932 is not a valid
encoding name
grzm$ createdb shift_jis --encoding Windows932
createdb: database creation failed: ERROR: Windows932 is not a valid
encoding name
grzm$ psql postgres
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

postgres=# select version();

version
------------------------------------------------------------------------
----------------------------------------------------------------------
PostgreSQL 8.1.4 on powerpc-apple-darwin8.6.0, compiled by GCC
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.
build 5341)
(1 row)

postgres=# create database shift_jis with encoding 'SHIFT_JIS';
ERROR: SHIFT_JIS is not a valid encoding name
postgres=# create database shift_jis with encoding 'SJIS';
ERROR: SJIS is not a valid encoding name

Michael Glaesemann
grzm seespotcode net




---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

I wrote:
> Michael Glaesemann <grzm@seespotcode.net> writes:
>> Just to confirm, it does look like there's a discrepancy between what
>> is in the documentation and the actual behavior of the server. The
>> documentation indicates that SJIS is a valid server encoding:

> This is a documentation error --- SJIS is certainly not a valid server
> encoding (it's not 8-bit-safe). Will fix --- thanks for pointing it out.

Actually, table 21-2 does say that SJIS isn't supported as a server
encoding, but the text at the top of the page (before table 21-1) is
pretty misleading --- it implies that every character set we have
is allowed as a server-side encoding. I'm going to change that text,
and also add a column to table 21-1 marking the supported server
encodings.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Jul 29, 2006, at 0:20 , Tom Lane wrote:

> I'm going to change that text,
> and also add a column to table 21-1 marking the supported server
> encodings.

Thanks, Tom.

Michael Glaesemann
grzm seespotcode net




---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Michael Glaesemann <grzm@seespotcode.net> writes:
> Just to confirm, it does look like there's a discrepancy between what
> is in the documentation and the actual behavior of the server. The
> documentation indicates that SJIS is a valid server encoding:

This is a documentation error --- SJIS is certainly not a valid server
encoding (it's not 8-bit-safe). Will fix --- thanks for pointing it out.

> createdb: database creation failed: ERROR: SJIS is not a valid
> encoding name

I wonder if it would be worth changing the code so that you get a
complaint saying the encoding is known but not allowed on the server
side. It hasn't come up before, so maybe it's not worth the trouble
.... but this message seems a bit confusing.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend