Re: BUG #3819: UTF8 can't handle \000 - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #3819: UTF8 can't handle \000
Date
Msg-id 200712170928.lBH9SvG23916@momjian.us
Whole thread Raw
In response to BUG #3819: UTF8 can't handle \000  ("Franklin Schmidt" <fschmidt@gmail.com>)
Responses Re: BUG #3819: UTF8 can't handle \000
List pgsql-bugs
Franklin Schmidt wrote:
> On Dec 17, 2007 12:54 AM, Bruce Momjian <bruce@momjian.us> wrote:
> >
> > Uh, as far as I know 0x00 is not a valid UTF8 byte value.
>
>
> I think it is a valid value.  RFC 3629 says:
>
> "Character numbers from U+0000 to U+007F (US-ASCII repertoire)
> correspond to octets 00 to 7F (7 bit US-ASCII values)."
>
> http://www.faqs.org/rfcs/rfc3629.html

Well, I realize 0x00 is a valid ASCII value and therefore a valid UTF8
value but we have never had anyone complain they can't store the 0x00
character because it doesn't mean anything in ASCII.  They use bytea to
store binary data like 0x00.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #3819: UTF8 can't handle \000
Next
From: "Franklin Schmidt"
Date:
Subject: Re: BUG #3819: UTF8 can't handle \000