Re: postgres8.3beta encodding problem?

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