On Monday, December 26, 2011 9:32:41 pm Adarsh Sharma wrote:
Thanks for the Explaination,
I find it hard to determine the way to store data in different encodings
to store in postgresql, below is the demo of some data :-
INSERT INTO conceptnet_frame
HI Ardash!
INSERT INTO conceptnet_frame
VALUES(3884,'ja','{1}は{2}を持っている。',16,3,2140,NULL,NULL,NULL);
Can you still access the database that produced the dump? If so, you may
want to produce a number of dumps for distinct language values. Japanese,
in particular, is a very complicated
On 26 Dec 2011, at 8:22, Adarsh Sharma wrote:
Dear all,
I am facing a unique issue when I try to load an sql into a postgresql
database :-
Actually, your issue isn't unique at all. You'll find it reoccurs on this list
regularly, although perhaps less frequent these days.
I faced an
Thanks for the Explaination,
I find it hard to determine the way to store data in different encodings
to store in postgresql, below is the demo of some data :-
INSERT INTO conceptnet_frame
VALUES(3884,'ja','{1}?{2}???',16,3,2140,NULL,NULL,NULL);
INSERT INTO conceptnet_frame
On 12/26/11 9:32 PM, Adarsh Sharma wrote:
Above link shows the above encoding schemes is in utf16 format but
postgresql-8.4 doesn't support it.
Is there any way to store data in different encoding in a utf-8 database.
afaik, anything in UTF16 can be represented by UTF8, but the inverse is
Dear all,
I am facing a unique issue when I try to load an sql into a postgresql
database :-
ERROR: invalid byte sequence for encoding UTF8: 0xe32720
HINT: This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
Dear all,
I am facing a unique issue when I try to load an sql into a postgresql
database :-
ERROR: invalid byte sequence for encoding UTF8: 0xe32720
HINT: This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
