Re: BUG #4007: chr(0) doesn't work anymore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Steve Clark" <sclark(at)netwolves(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4007: chr(0) doesn't work anymore
Date: 2008-03-03 15:49:39
Message-ID: 23476.1204559379@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

"Steve Clark" <sclark(at)netwolves(dot)com> writes:
> Until 8.3.0 the following worked:
> SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
> 'default_unit_key';

It would have "worked" only for rather small values of "work", since
most of the support for type TEXT isn't null-safe. Try something like
"select chr(0) || 'foo';" for example. Wouldn't an empty string do what
you want better?

> it now fails with:
> ERROR: null character not permitted

This is an intentional change and won't be undone, at least not until
TEXT is null-safe, which isn't likely to happen in the foreseeable future.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-03-03 15:54:24 Re: BUG #4006: pg_ctl assumes that all config files lie in data_directory
Previous Message Steve Clark 2008-03-03 15:28:04 BUG #4007: chr(0) doesn't work anymore

Browse pgsql-patches by date

  From Date Subject
Next Message Steve Clark 2008-03-03 16:21:10 Re: BUG #4007: chr(0) doesn't work anymore
Previous Message Steve Clark 2008-03-03 15:28:04 BUG #4007: chr(0) doesn't work anymore