Re: [pgadmin-hackers] CVS compile error
Le Mercredi 8 Octobre 2003 09:06, Dave Page a crit : Could that be something to do with the lack of Unicode support on Mac? MacOsX has built-in support for Unicode. wxMac does not. It remains to be added to wxMac according to Stefan. Cheers, Jean-Michel ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] CVS compile error
Stefan Csomor wrote: Hi it is not really difficult but if you don't know the MacOS Unicode calls it's getting tiresome, I will try to make an assessment of the trouble involved in solving this for 10.2 by next week, I see we need it... Thanks, Stefan, we really appreciate your continuing support. Let me know if there is anything I can do to help you. ahp ---(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
Re: [pgadmin-hackers] Degrade(character conversion problem) pga3?
Hi Andreas. It is a little strange... pgSet *pgConn::ExecuteSet(const wxString sql) { // Execute the query and get the status. PGresult *qryRes; wxLogSql(wxT(Set query (%s:%d): %s), this-GetHost().c_str(), this-GetPort(), sql.c_str()); qryRes = PQexec(conn, sql.mb_str(wxConvUTF8)); When this conv is made wxConvUTF8, a problem doesn't come out. why?? It is ignored though this connection thread has already been set up. Does it know anything though it tries to go on? Logging is sent by separate mail. regards, Hiroshi Saito From: Andreas Pflug [EMAIL PROTECTED] 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/pgadmin3/20030922_1.jpg http://cre-ent.skcapi.co.jp/~saito/pgadmin3/20031007_1.jpg Tonight, let me know it if you know something though it will be examined. Thank you. There's obviously something wrong... How about the error log? ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Degrade(character conversion problem) pga3?
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/pgadmin3/20030922_1.jpg http://cre-ent.skcapi.co.jp/~saito/pgadmin3/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 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 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] [pgadmin-hackers] Degrade(character conversion problem) pga3?
Hi Andreas. It was ascertained. The timing of constructer of pgConn isn't suitable for it. It tried to trace it in let's as below. pgSet *pgConn::ExecuteSet(const wxString sql) { // Execute the query and get the status. PGresult *qryRes; wxLogSql(wxT(Set query (%s:%d): %s), this-GetHost().c_str(), this-GetPort(), sql.c_str()); if (conv == wxConvUTF8) wxLogSql(wxT(DEBUG: conv=wxConvUTF8)); else if (conv == wxConvLibc) wxLogSql(wxT(DEBUG: conv=wxConvLibc)); else wxLogSql(wxT(DEBUG: conv=others)); qryRes = PQexec(conn, sql.mb_str(conv)); --- All results are DEBUG: conv=wxConvLibc. I think how it will be modified. any comment? regards, Hiroshi Saito - Original Message - From: Hiroshi Saito [EMAIL PROTECTED] 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. ---(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