Re: Problems using PGAdmin III
От | Andreas Pflug |
---|---|
Тема | Re: Problems using PGAdmin III |
Дата | |
Msg-id | 3F9C1086.5020704@pse-consulting.de обсуждение исходный текст |
Ответ на | Problems using PGAdmin III (Együd Csaba <csegyud@vnet.hu>) |
Ответы |
Re: Problems using PGAdmin III
|
Список | 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
В списке pgadmin-support по дате отправления: