Skip site navigation (1) Skip section navigation (2)

Re: Usind database with encoding UNICODE and vovel

From: Johann Zuschlag <zuschlag2(at)online(dot)de>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Usind database with encoding UNICODE and vovel
Date: 2005-08-04 10:30:52
Message-ID: 42F1EE5C.5060404@online.de (view raw or flat)
Thread:
Lists: pgsql-odbc
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I used:<br>
<br>
Debian Sarge with PostgreSQL 7.4.7<br>
My application on Win XP SP2<br>
ODBC-driver: 08.01.1003<br>
<br>
More or less the same problem with LATIN1 (server) and UNICODE (client)<br>
but PgAdminIII doesn't show <b>&auml;&ouml;&uuml;&szlig;</b> later.<br>
<span class="150583209-04082005"></span><br>
Regards<br>
<br>
Johann<br>
<br>
Josef Springer schrieb:<br>
<br>
<blockquote cite="mid42F1AFEC(dot)1020906(at)joops(dot)com" type="cite"> Using no
vovels (umlaut) work fine. But using a vovel, curious effect.<br>
I have tried all server and client variations with sense with this
result. All tests are done with a string column containing <b>&auml;&ouml;&uuml;&szlig;</b><br>
  <table border="1" cellpadding="2" cellspacing="2" width="100%">
    <tbody>
      <tr>
        <td valign="top">Server database encoding<br>
        </td>
        <td valign="top">Client encoding<br>
        </td>
        <td valign="top">Result<br>
        </td>
      </tr>
      <tr>
        <td valign="top">LATIN<br>
        </td>
        <td valign="top">LATIN<br>
        </td>
        <td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0<br>
        </td>
      </tr>
      <tr>
        <td valign="top">LATIN<br>
        </td>
        <td valign="top">UNICODE</td>
        <td valign="top">Reading works bur witing gets an error 'Bad
code xxx for &nbsp;UNICODE'<br>
        </td>
      </tr>
      <tr>
        <td valign="top">UNICODE<br>
        </td>
        <td valign="top">UNICODE<br>
        </td>
        <td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0<br>
        </td>
      </tr>
      <tr>
        <td valign="top">UNICODE<br>
        </td>
        <td valign="top">LATIN<br>
        </td>
        <td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0<br>
        </td>
      </tr>
      <tr>
        <td valign="top">UNICODE<br>
        </td>
        <td valign="top">WIN1250<br>
        </td>
        <td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0</td>
      </tr>
      <tr>
        <td valign="top">SQL_ASCII<br>
        </td>
        <td valign="top">UNICODE<br>
        </td>
        <td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0<br>
        </td>
      </tr>
    </tbody>
  </table>
  <br>
</blockquote>
<b>In PgAdminIII the column is displayed correct in all server database
variations !</b><br>
<br>
</body>
</html>


Attachment: unknown_filename
Description: text/html (2.6 KB)

In response to

pgsql-odbc by date

Next:From: Alejandro D. BurneDate: 2005-08-04 10:44:04
Subject: Re: Usind database with encoding UNICODE and vovel
Previous:From: Dave PageDate: 2005-08-04 10:24:03
Subject: Re: New libpq driver snapshot

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group