Re: postgres8.3beta encodding problem?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres8.3beta encodding problem?
Date: 2007-12-17 18:13:54
Message-ID: 1197915234.28804.325.camel@dogma.ljc.laika.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 2007-12-17 at 13:53 -0300, marcelo Cortez wrote:
> select chr(165);
> ERROR: requested character too large for encoding:
> 165
> it's one old scrip if not remember wrong works
> postgres in 8.2.4
> any clue?

http://www.postgresql.org/docs/8.3/static/release-8-3.html

"Ensure that chr() cannot create invalidly-encoded values (Andrew)

In UTF8-encoded databases the argument of chr() is now treated as a
Unicode code point. In other multi-byte encodings chr()'s argument must
designate a 7-bit ASCII character. Zero is no longer accepted. ascii()
has been adjusted to match."

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sam Mason 2007-12-17 18:23:16 Re: Efficiency vs. code bloat for SELECT wrappers
Previous Message Colin Wetherbee 2007-12-17 17:49:46 Re: Efficiency vs. code bloat for SELECT wrappers