RE: [BUGS] Problem with 7.0.3 dump -> 7.1b4 restore - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject RE: [BUGS] Problem with 7.0.3 dump -> 7.1b4 restore
Date
Msg-id 20010228110220G.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: [BUGS] Problem with 7.0.3 dump -> 7.1b4 restore  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Problems with Multibyte in 7.1 beta?  ("Rainer Mager" <rmager@vgkk.com>)
Dead locks  ("Rainer Mager" <rmager@vgkk.com>)
RE: [BUGS] Problem with 7.0.3 dump -> 7.1b4 restore  ("Rainer Mager" <rmager@vgkk.com>)
List pgsql-hackers
> Attached is a single INSERT that shows the problem. The character after the
> word "Fiber" truncates the text when using JDBC. NOTE, the text IS in the
> database, that is, the dump/restore seems ok, the problem is when trying to
> read the text later. The database is UTF8 and I just tested with beta 5.
> 
> Oh, BTW, if I try to set (INSERT) this same character via JDBC and then
> retreive it again then everything is fine.

I have tested your data using psql:

unicode=# create table pr_prop_info(i1 int, i2 int, i3 int, t text);
CREATE
unicode=# \encoding LATIN1
unicode=# \i example.sql 
INSERT 2378114 1
unicode=# select * from pr_prop_info;

The character after the word "Fiber" looks like "­Optic Cable". So as
long as the server/client encoding set correctly, it looks ok. I guess
we have some problems with JDBC driver. Unfortunately I am not a Java
guru at all. Can anyone look into our JDBC driver regarding this
problem?
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: RE: [BUGS] Problem with 7.0.3 dump -> 7.1b4 restore
Next
From: Thomas Lockhart
Date:
Subject: Re: Release in 2 weeks ...