AW: MULTIBYTE and SQL_ASCII (was Re: [JDBC] Re: A bug w ith pgsql 7.1/jdbc and non-ascii (8-bit) chars?)

Tom's suggestion does not sound reasonable to me. If PostgreSQL is not
built with MULTIBYTE, then it means there would be no such idea
"encoding" in PostgreSQL becuase there is no program to handle
encodings. Thus it would be meaningless to assign an "encoding" to a
database if MULTIBYTE is not enabled.

Why? Without the MULTIBYTE code, the backend cannot perform character
set translations --- but it's perfectly possible that someone might not
need translations. A lot of European sites are probably very happy
as long as the server gives them back the same 8-bit characters they
stored.

Yes, that is what we do (German language). Encoding is Latin1.
Would it not be reasonable to return the machine LC_CTYPE in the non multibyte case ?

Andreas