Re: [pgadmin-hackers] client encoding SQL_ASCII for server SQL_ASCII

2003-10-01 Thread Hiroshi Saito
It is this problem. any comment? regards, Hiroshi Saito - Original Message - From: "Hiroshi Saito" <[EMAIL PROTECTED]> > > There is no error in every place. > But, there is one place of the problem. > It is a quote problem by the renewal of data view. > > regards, > Hiroshi Saito f

Re: [pgadmin-hackers] client encoding SQL_ASCII for server SQL_ASCII

2003-10-01 Thread Hiroshi Saito
There is no error in every place. But, there is one place of the problem. It is a quote problem by the renewal of data view. regards, Hiroshi Saito - Original Message - From: "Hiroshi Saito" <[EMAIL PROTECTED]> > Hmm.. > > From: "Andreas Pflug" <[EMAIL PROTECTED]> > > > > Dave Page

Re: [pgadmin-hackers] client encoding SQL_ASCII for server SQL_ASCII

2003-10-01 Thread Hiroshi Saito
Hmm.. From: "Andreas Pflug" <[EMAIL PROTECTED]> > Dave Page wrote: > > >Should that be back patched for 1.0.1? Seems like a bug to me. > > > > > > > > The bug is the non-ascii data... > Yes, we should back-patch that. Just plain pgConn.cpp and pgConn.hpp. > > Regards, > Andreas Please wait

Re: [pgadmin-hackers] client encoding SQL_ASCII for server SQL_ASCII

2003-10-01 Thread Andreas Pflug
Dave Page wrote: Should that be back patched for 1.0.1? Seems like a bug to me. The bug is the non-ascii data... Yes, we should back-patch that. Just plain pgConn.cpp and pgConn.hpp. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9

Re: [pgadmin-hackers] Client Encoding

2003-06-11 Thread Dave Page
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 11 June 2003 14:30 > To: Dave Page; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] Client Encoding > > > Dave Page wrote: > > >Sounds good. They only problem with Uni

Re: [pgadmin-hackers] Client Encoding

2003-06-11 Thread Andreas Pflug
Dave Page wrote: Sounds good. They only problem with Unicode builds will (==should) be Win9x... I don't believe Win9x is a preferred administrator's os... :-> Let's wait and see if there are really many people trying to run pgAdmin3 under these ancient os. Regards, Andreas --

Re: [pgadmin-hackers] Client Encoding

2003-06-11 Thread Dave Page
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 11 June 2003 13:52 > To: [EMAIL PROTECTED]; Jean-Michel POURE; Dave Page > Subject: Re: [pgadmin-hackers] Client Encoding > > > Dave Page wrote: > > >It seems we all seem to

Re: [pgadmin-hackers] Client Encoding

2003-06-11 Thread Andreas Pflug
Dave Page wrote: It seems we all seem to think that client_encoding should be set to UNICODE in all cases for unicode builds and SQL_ASCII for others, therefore I've backed out the previous changes and implemented this behaviour instead. Looks good to me. I've changed libpq handling so utf-8 is

Re: [pgadmin-hackers] Client Encoding

2003-06-10 Thread Hiroshi Saito
Hi Dave. They are still imperfect. This binary understands SJIS-code more securely than UNICODE now. http://cre-ent.skcapi.co.jp/~saito/pgadmin/lib/pgadmin3_2003-06-10_bin.zip Of course, other encodings are understood, too. Leave it because it is input and output of the local data and it doesn't b