On 04 May 2001 11:40:48 -0400, Tom Lane wrote:

> But a non-MULTIBYTE backend doesn't even have the concept of "setting
> the encoding" --- it will always just report SQL_ASCII.

What kind of error message does "createdb -E LATIN1" give on a non
MULTIBYTE backend? 

Maybe there needs to be a note somewhere informing people from Europe
that they too need MULTIBYTE as an option at compile time. i.e. In a
bright yellow box in the HTML docs...

And in the Reference manual and man pages the -E option for createdb
needs a note to specify that it applies to MULTIBYTE backends only. 


Tony Grant

RedHat Linux on Sony Vaio C1XD/S

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to