dbTalk Databases Forums  

Re: [BUGS] [pgadmin-hackers] Degrade(character conversion problem) pga3?

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss Re: [BUGS] [pgadmin-hackers] Degrade(character conversion problem) pga3? in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Andreas Pflug
 
Posts: n/a

Default Re: [BUGS] [pgadmin-hackers] Degrade(character conversion problem) pga3? - 10-08-2003 , 12:52 PM






This is a multi-part message in MIME format.
--------------080903060304040300090501
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hiroshi Saito wrote:

Quote:
Hi Andreas.

I have a problem.
It is a happening within this week.

See below.
http://cre-ent.skcapi.co.jp/~saito/p...20030922_1.jpg
http://cre-ent.skcapi.co.jp/~saito/p...20031007_1.jpg

Tonight, let me know it if you know something though it will be examined.
Thank you.



Hi Hiroshi,

AFAICS this is a backend problem. I re-posted this on pgsql-bugs too,
the attached log is your's, reduced to the relevant part. Please check
the query in the Query Tool, try to modify the column name which seems
to provoke this problem.
Maybe you found a bug in the EUC_JP <-> UTF-8 conversion.

Regards,
Andreas

--------------080903060304040300090501
Content-Type: text/plain;
name="pgadmin.log"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline;
filename="pgadmin.log"


2003-10-09 01:25:27 QUERY : Set query (128.77.50.202:5432): SELECT null_frac AS "Null Fraction", avg_width AS "Average Width", n_distinct AS "Distinct Values", most_common_vals AS "Most Common Values", most_common_freqs AS "Most Common Frequencies", histogram_bounds AS "Histogram Bounds", correlation AS "Correlation"
FROM pg_stats
WHERE schemaname = 'public'
AND tablename = 'stimsdb'
AND attname = '要**別番'
2003-10-09 01:25:27 QUERY : WARNING: UtfToLocal: could not convert UTF-8 (0xca94). Ignored
2003-10-09 01:25:27 QUERY : WARNING: UtfToLocal: could not convert UTF-8 (0xd427). Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9776) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9166) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9522) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 ERROR : ERROR: parser: unterminated quoted string at or near "'・ッ at character 351



--------------080903060304040300090501
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

--------------080903060304040300090501--



Reply With Quote
  #2  
Old   
Hiroshi Saito
 
Posts: n/a

Default Re: [BUGS] [pgadmin-hackers] Degrade(character conversion problem) pga3? - 10-08-2003 , 01:40 PM






Hi Andreas.

Hmm..
It is thought still to be bug on this side.
Or, wxWindows.
When the code is analyzed, it seems to be the below.

With the SJIS
9776 9166 8eaf 95ca 94d4

With the EUC_JP
d7cd c7c1 b1bc ccca d6c8

With the UNICODE
feff 8981 7d20 8b58 5225 756a

When it is probably delivered, it fails the change.

regards,
Hiroshi Saito

----- Original Message -----
From: "Andreas Pflug" <pgadmin (AT) pse-consulting (DOT) de>


Quote:
Hiroshi Saito wrote:

Hi Andreas.

I have a problem.
It is a happening within this week.

See below.
http://cre-ent.skcapi.co.jp/~saito/p...20030922_1.jpg
http://cre-ent.skcapi.co.jp/~saito/p...20031007_1.jpg

Tonight, let me know it if you know something though it will be examined.
Thank you.




Hi Hiroshi,

AFAICS this is a backend problem. I re-posted this on pgsql-bugs too,
the attached log is your's, reduced to the relevant part. Please check
the query in the Query Tool, try to modify the column name which seems
to provoke this problem.
Maybe you found a bug in the EUC_JP <-> UTF-8 conversion.

Regards,
Andreas


--------------------------------------------------------------------------------


Quote:
2003-10-09 01:25:27 QUERY : Set query (128.77.50.202:5432): SELECT null_frac AS "Null Fraction", avg_width AS "Average
Width", n_distinct AS "Distinct Values", most_common_vals AS "Most Common Values", most_common_freqs AS "Most Common
Frequencies", histogram_bounds AS "Histogram Bounds", correlation AS "Correlation"
Quote:
FROM pg_stats
WHERE schemaname = 'public'
AND tablename = 'stimsdb'
AND attname = '要 *~^.'
2003-10-09 01:25:27 QUERY : WARNING: UtfToLocal: could not convert UTF-8 (0xca94). Ignored
2003-10-09 01:25:27 QUERY : WARNING: UtfToLocal: could not convert UTF-8 (0xd427). Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9776) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9166) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 QUERY : WARNING: LocalToUtf: could not convert (0x9522) EUC_JP to UTF-8. Ignored
2003-10-09 01:25:27 ERROR : ERROR: parser: unterminated quoted string at or near "'fッ at character 351


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.