Re: Problems using PGAdmin III

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: csegyud(at)vnet(dot)hu
Cc: "Pgadmin-Support (E-mail)" <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Problems using PGAdmin III
Date: 2003-10-26 18:20:54
Message-ID: 3F9C1086.5020704@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Együd Csaba wrote:

>Dear Jean-Michel,
>I'm succeeded to subscribe this list. Thank you.
>
>
>
>>You can register the support mailing list from:
>>http://www.pgadmin.org/pgadmin3/support.php#support_list
>>
>>
>Done.
>
>
>
>>The euro display problem is an encoding problem. The euro sign is not part
>>
>>
>of
>
>
>>an ASCII database. Whenever you would like Euro support, choose:
>>
>>Database->Create Database and select dropdown menu:
>>Latin9 (Iso-8859-15) or Unicode encoding.
>>
>>
>To tell the truth it wasn't what I wnated. Actually I can insert the euro
>sign via ODBC using pure SQL_ASCII encoding. PGAdmin can display the euro
>sign. The only problem is that it can't display which was inserted with it.
>I can't use unicode encoding, because the client machines are win9x which
>does not support unicode (as far as I know). It's not a crucial problem, but
>it's an inconvenience.
>
>
You *can* use unicode, if you set the client encoding to a codeset your
machine supports (might be Latin9). SQL_ASCII looks convenient, but when
it comes to multilanguage it's a real pain, so it's better to designate
what the data really is.

Regards,
Andreas

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message pgadmin 2003-10-27 03:20:47 How to use the SET data type? Help plz!
Previous Message Együd Csaba 2003-10-26 18:02:13 Problems using PGAdmin III