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
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 fa
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 y
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(wxConv
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 suppo
On Wednesday, Oct 8, 2003, at 05:28 US/Eastern, Stefan Csomor wrote:
Hi
actually it is the other way round :
wxMac supports unicode, but the necessary w-char headers are only
available
on 10.3 or when using the CodeWarrior development tools. What is
needed to
make wxMac supporting unicode with
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 y
Hi
actually it is the other way round :
wxMac supports unicode, but the necessary w-char headers are only available
on 10.3 or when using the CodeWarrior development tools. What is needed to
make wxMac supporting unicode with the gcc toolchain is to write a
replacement for all w... functions need
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 bro
> -Original Message-
> From: Adam H.Pendleton [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 02:34
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] CVS compile error
>
>
> I still get this compile error, on Mac, with the CVS HEAD from both
> pgadmin3 and wxWindows:
>
> utils/u
10 matches
Mail list logo