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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 17:11:43
Message-ID: 200803031711.m23HBht20068@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

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

Attachment Content-Type Size
/rtmp/diff text/x-diff 1.2 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2008-03-03 17:12:16 Re: BUG #4006: pg_ctl assumes that all config files lie in data_directory
Previous Message Tom Lane 2008-03-03 16:28:11 Re: BUG #4007: chr(0) doesn't work anymore

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2008-03-03 17:12:44 Re: CopyReadAttributesCSV optimization
Previous Message Tom Lane 2008-03-03 16:28:11 Re: BUG #4007: chr(0) doesn't work anymore