From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "claus" <ch(at)greenmail(dot)ch>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: ConnSettings |
Date: | 2003-08-14 13:22:07 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B465@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: claus [mailto:ch(at)greenmail(dot)ch]
> Sent: 14 August 2003 14:15
> To: pgadmin-hackers(at)postgresql(dot)org
> Cc: Dave Page
> Subject: Re: [pgadmin-hackers] ConnSettings
>
>
> OK I will try pgadmin III beta I think it is stable enough for me.
>
> Nevertheless if I execute
> SET CLIENT_ENCODING = LATIN1;
> in an SQL Window the character display is fine even in
> pgadmin II since the translation is (I guess) done by the
> server process and vb just diplays character it can display.
> So I thought the ConnSetting does the same but it seems not
> to be used.
It depends on the character set. It'll most likely fail miserably if you
have multibyte charactersets such as EUC_JP or JOHAB.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Raphaël Enrici | 2003-08-14 13:59:24 | pgA3 desktop integration |
Previous Message | claus | 2003-08-14 13:15:08 | Re: ConnSettings |