[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Bug in UTF8-Validation Code?
From:       "Albe Laurenz" <all () adv ! magwien ! gv ! at>
Date:       2007-04-04 8:34:52
Message-ID: AFCCBB403D7E7A4581E48F20AF3E5DB20203E424 () EXADV1 ! host ! magwien ! gv ! at
[Download RAW message or body]

> When the database uses a single byte encoding, the chr function takes
> the binary byte representation as an integer number between 0 and 255
> (e.g. ascii code).
> When the database encoding is one of the unicode encodings it takes a
> unicode code point.
> This is also what Oracle does.

Sorry, but this is *NOT* what Oracle does.
At least if we can agree that the code point for the Euro sign
is 0x20AC.

SQL> SELECT ASCII('EUR') AS DEC,
  2         TO_CHAR(ASCII('EUR'), 'XXXXXX') AS HEX
  3  FROM DUAL;

       DEC HEX
---------- ----------------------------
  14844588  E282AC

The encoding in this example is AL32UTF8, which corresponds to
our UTF8.

Yours,
Laurenz Albe

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

[prev in list] [next in list] [prev in thread] [next in thread]