| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Steve Clark <sclark(at)netwolves(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #4007: chr(0) doesn't work anymore |
| Date: | 2008-03-03 18:02:57 |
| Message-ID: | 47CC3D51.1020708@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Bruce Momjian wrote:
> Tom Lane wrote:
>
>> Steve Clark <sclark(at)netwolves(dot)com> writes:
>>
>>> I'm not sure I understand what you mean about TEXT being null-safe.
>>> What are the issues, and why was
>>> it supported for years and now abruptly changed.
>>>
>> It never was supported, we are simply plugging a hole that let you
>> create a text value that would be likely to malfunction in subsequent
>> use.
>>
>
> Seems we never documented that chr(0) is not supported. I have applied
> the following doc patch to CVS HEAD and 8.3.X.
>
>
> The NULL (0) character is not
> allowed because text data types cannot reliably store such bytes.
>
>
"Reliably" is arguably misleading here.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-03-03 18:09:10 | Re: [BUGS] BUG #4007: chr(0) doesn't work anymore |
| Previous Message | Bruce Momjian | 2008-03-03 17:12:16 | Re: BUG #4006: pg_ctl assumes that all config files lie in data_directory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-03-03 18:09:10 | Re: [BUGS] BUG #4007: chr(0) doesn't work anymore |
| Previous Message | Bruce Momjian | 2008-03-03 17:13:19 | Re: sinval.c / sinvaladt.c restructuring |