Actually, it's a wording issue: ASCII: 7-bit Extended ASCII (Latin 1): 8-bit
Personally, whenever i say ASCII, i usually mean Extended ASCII.
Regards.
Tino Wildenhain wrote:
Hi Albin,
Albin Blaschka wrote:
Hello,
I am confronted with a little problem in pgadmin III:
Table cells and comments on database objects are not properly displayed if they contain a german umlaut.
The table cells just contain ", the comments (on tables,
for example) are completly empty.
In pgadmin II everything is okay, if I connect via
ODBC/Access to the tables, the umlauts are properly
displayed, too.
Plattform for pgadmin: Win 2000 Database: Postgres 7.3.2 on Debian Linux Woody (3.0), Database encoding SQL_ASCII
^^^^^^^^^^
This is wrong. You cant have Umlauts with ASCII. If you input them, you violate the ASCII codeset, wich is 7 Bit only. You'll have to recode your data to ISO8859-1 (Latin-1) or any superset (UNICODE) Then pgadminIII works as well as any other application. For migration or your apps they should just set their client_encoding to iso8859-1 then (if you choose UNICODE)
Regards Tino Wildenhain
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
-- Sincerely, Reshat.
-------------------------------------------------------------------------------------------
If you see my certificate with this message, you should be able to send me encrypted e-mail. Please consult your e-mail client for details if you would like to do that.
smime.p7s
Description: S/MIME Cryptographic Signature
