Hello,
If you are loading this command from a UTF-8 file, then try saving this file
without Unicode signature. I had to remove the signature in order to prosess
scripts in Oracle SQLPlus.
Yuri
-----Original Message-----
From: Kallol Nandi [mailto:kallol.nandi@indussoft.com]
Sent: Friday, July 18, 2003 12:22 PM
To: Pgsql-General
Subject: Re: [GENERAL] (Urgent) Regarding double byte support
Hi Tino,
The initdb has created a database cluster with default encoding as
SQL_ASCII.
I have created a database in this data directory with UNICODE encoding using
the command :
createdb -E UNICODE dbname.
I created a table in the database with a varchar field.
But when I try to insert japanese characters in the field i get the
following error :
i>?insert into ttable values('a?ScYYa,%a?>');
ERROR: parser: parse error at or near "i>?insert"
What is the problem here. Is it the installation? Any pointers will be
highly appreciated.
One more thing :
In all documentations that I find it is mentioned that to enable multibyte
you have to run the following command
./configure --enable-multibyte='encoding'
But configure file itself is not there.
Can you send me the detailed instructions.
As mentioned earlier has it do with some config file or the installation
procedure.
Thanks and Regards,
Kallol.
-----Original Message-----
From: Tino Wildenhain [mailto:tino@wildenhain.de]
Sent: Friday, July 18, 2003 6:49 PM
To: Kallol Nandi
Subject: Re: [GENERAL] Regarding double byte support
Hi Kallol Nandi,
Kallol Nandi wrote:
> Does Postgresql 7.2.1 support double byte characters?
> If yes is then how to define fields that will contain double byte
> characters?
Although you could define your own type, you can use the database with
UNICODE encoding (during creation) then all text/char fields are utf8.This
works pretty well for all languages.
Hoever there are also different encodings available,I dont know how it is
with chinese or such. But probably its mapped internally to utf8 anyway.
Regards
Tino Wildenhain
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match